Perl 6 - the future is here, just unevenly distributed

IRC log for #marpa, 2014-02-13

| Channels | #marpa index | Today | | Search | Google Search | Plain-Text | summary

All times shown according to UTC.

Time Nick Message
00:00 ronsavage1 joined #marpa
02:17 jeffreykegler1 joined #marpa
03:29 jeffreykegler joined #marpa
04:30 ronsavage joined #marpa
05:47 ronsavage left #marpa
16:57 jeffreykegler joined #marpa
17:51 * lucs continues reading the Semantics POD...
17:52 lucs It's not clear from that doc why bail() can take an array ref instead of a simple message :/
17:55 jeffreykegler lucs: Actually, any object, not just an array, I think.
17:55 jeffreykegler Using exception objects is the trend ...
17:55 jeffreykegler and unlike many fashions, actually a good idea ...
17:56 jeffreykegler Marpa does not use exception objects internally because of 5.10.0 compatibility, ...
17:56 lucs But the program still dies, right? Is the idea to grab the object in an eval or something?
17:56 jeffreykegler but I encourage their use by others. :-)
17:57 jeffreykegler Yes, the idea is to grab the object, and be able to do more with it than simply print it somewhere.  Damien's _Perl Best Practices_ book goes on at length about this, ...
17:57 jeffreykegler as do many other folks.
17:57 jdurand joined #marpa
17:57 lucs jeffreykegler: Okay, makes sense. Thanks.
17:59 jeffreykegler lucs: An example of where exception objects could be used in Marpa is parse errors -- these can occur in context of the NAIF, or of the SLIF.
17:59 jeffreykegler But each has a very different idea of location from the other ...
17:59 jeffreykegler With exception objects, you throw a blessed object and a layer which is smart about location can catch it and do the final formatting ...
18:00 jeffreykegler you can do the same with string concatenation, but it's not as nice.
18:00 lucs Yes, I see, interesting.
18:37 jdurand_ joined #marpa
22:21 ronsavage joined #marpa

| Channels | #marpa index | Today | | Search | Google Search | Plain-Text | summary