On Thu, Sep 18, 2014 at 11:21 PM, Jeffrey Kegler < [email protected]> wrote:
> Sounds like a good idea. I was put off by the big red icon they used, > which I thought overdid it, but apparently they are going to fix that. > Yes, we can also add homepage, like Catalyst <https://metacpan.org/pod/Catalyst>. Could you prepare a patch? > Sure, here goes — https://github.com/jeffreykegler/Marpa--R2/pull/180. My current focus is a rewrite of the Marpa::R2 doc's description of SLIF > parse events. A question on the IRC channel got me reading my own docs. > The descriptions of SLIF parse events are scattered thru the docs. And, > once a diligent reader chases the all of them down, the wording is often > not the clearest. > SLIF parse events evolved in two stages: "pauses", then "named events", and > both terms are intermixed. I'm reworking the language so they're always > called "events". The new, full name is "SLIF parse events" and this is > used when the context does not make it clear what is meant by "event". > There are other vocabulary improvements -- for example, parse events are > now to "trigger", and that term will be used consistently. And there'll be > a new POD page dedicated to parse events, as an overview for someone trying > to get started. > It's a good thing and certainly makes things clearer. Some humble editorial suggestions are below. event-active (method) event-aware? zero-length instance of a symbol > zero-length symbol instance is recognized occurrence? completion event triggers occur whenever completion events trigger whenever I hope when this is done, there are fewer obstacles to those of you who > want to use parse events. They are something totally new in parsing, and > have yet to be exploited to anything like their potential. I hope this doc > rewrite will help turn that around. > Sure, I also think the doc could benefit from some good examples. Off the top of my head, here are events' use cases/categories. conditional preservation of whitespace and others by Ron Savage processing lexemes before parse evaluation sl_json.t <https://github.com/jeffreykegler/Marpa--R2/blob/master/cpan/t/sl_json.t>, kkrev <http://irclog.perlgeek.de/marpa/2014-09-17#i_9374694> disambiguation not sure — C::AST <https://github.com/jddurand/MarpaX-Languages-C-AST/blob/master/lib/MarpaX/Languages/C/AST/Grammar/ISO_ANSI_C_2011.pm#L187> Jean-Damien Durand error recovery like in Marpa::HTML -- Ruby Slippers predated events, I think There are possibly others; perhaps they can be incorporated in the doc to connect theory to practice, so to say. Hope this helps, rns. > -- jeffrey > > > On 09/18/2014 01:01 PM, Ruslan Shvedov wrote: > > > http://blogs.perl.org/users/peter_rabbitson/2014/09/encourage-user-participation-via-a-single-line-patch-to-your-dist-metadata.html > > irc.freenode.net is supported, they say, so perhaps irc:// > irc.freenode.net/#marpa can be usefully displayed on Marpa::R2 metacpan > page? > -- > You received this message because you are subscribed to the Google Groups > "marpa parser" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > > > -- > You received this message because you are subscribed to the Google Groups > "marpa parser" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "marpa parser" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
