Perl 6 - the future is here, just unevenly distributed

IRC log for #marpa, 2014-09-20

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

All times shown according to UTC.

Time Nick Message
01:18 jeffreykegler joined #marpa
01:48 ilbot3 joined #marpa
01:48 Topic for #marpa is now Start here: http://savage.net.au/Marpa.html - Pastebin: http://scsys.co.uk:8002/marpa - Jeffrey's Marpa site: http://jeffreykegler.github.io/Marpa-web-site/ - IRC log: http://irclog.perlgeek.de/marpa/today
02:05 flaviu1 joined #marpa
02:05 flaviu1 hey, I just wanted to mention that I found https://jeffreykegler.github.i​o/Marpa-web-site/libmarpa.html a bit confusing
02:06 flaviu1 the link "the Marpa::R2 github repository" points to https://github.com/jeffreykegler/Marpa--R2, while it seems that libmarpa is at https://github.com/jeffreykegler/libmarpa
02:07 flaviu1 left #marpa
05:24 jeffreykegler joined #marpa
05:25 jeffreykegler ronsavage: rns suggests adding Marpa's "home page" to the META.yml file, so it shows up on MetaCPAN, etc.  That seems like a good idea.  I'm going to use your page, if that's OK.
05:27 jeffreykegler flaviu1: Don't know if I understand your point correctly, but Libmarpa and Marpa::R2 are two different things, which Marpa::R2 being built on top of Libmarpa.
05:28 jeffreykegler The Libmarpa page is designed for folks already to some extent familiar with Marpa.  Maybe I should add some warning language at the top ...
05:28 jeffreykegler such as "If you're here to learn about Marpa, this is not a good place to start.  Better would be http: ..."
05:29 jeffreykegler I don't want to clutter all the advanced pages with that kind of language, but perhaps it's appropriate for the top Libmarpa page.
06:23 lwa joined #marpa
06:25 lwa joined #marpa
06:44 jdurand joined #marpa
06:46 jdurand Jeffrey, during the recognizer phase, suppose that I have a MARPA_EVENT_SYMBOL_COMPLETED event for symbol X, where X is the LHS symbol of more than one rule, say X ::= Y and X::= Z. The only way to know which rule triggered the event is to call marpa_r_progress API family, am I right ?
08:17 pczarn joined #marpa
08:58 jeffreykegler joined #marpa
08:59 jeffreykegler jdurand: You could set up completion events for <Y> and <Z>
09:04 jeffreykegler jdurand: You can also create new symbols <X1> and <X2> and do as follows:
09:05 jeffreykegler X1 ::= Y  X2 ::= Z  X ::= X1 | X2 ...
09:05 jeffreykegler then check for completion of X1 and X2
10:25 jdurand Yep, thanks - maybe also yet another way: X ::= Y (nullable1); X ::= Z (nullable2) and check null events on nullable1 and nullable2
13:18 jeffreykegler joined #marpa
13:20 jeffreykegler jdurand: re http://irclog.perlgeek.de/​marpa/2014-09-20#i_9386821 -- TIMTOWDI !
13:21 jeffreykegler Yes, the reason events aren't rule-based is that, everything you'd want rule-oriented events to do, you can already do several ways with symbol-based events.
13:22 jeffreykegler In addition, at the time I designed the SLIF parse events, rules did not have names, so there was no reliable way to identify them.
14:02 lwa joined #marpa
19:40 jeffreykegler joined #marpa
22:34 ronsavage joined #marpa
22:44 ronsavage jeffreykegler: Definitely add Marpa's homepage to the metadata. As I release new versions, I'm slowly putting all my modules on github, and updating their Build.PLs and Makefile.PLs
23:43 shadowpaste "jeffreykegler" at 162.232.214.245 pasted "New example for events (difficult!)" (160 lines) at http://scsys.co.uk:8002/424684
23:44 jeffreykegler I've written up a new synopsis for the SLIF parse event POD I'm writing, and it's an example of why POD synopses sometimes cannot be good tutorials.
23:44 jeffreykegler It's devoted to "corner cases", and so the grammar is actually quite bizarre, and unlike anything you'd actually write.
23:44 jeffreykegler The doc once finished will deal with everything in it, but for example --
23:45 jeffreykegler Q: What happens with parse events if the grammar is ambiguous?
23:45 jeffreykegler A: You see all the possibilities?
23:45 jeffreykegler Q: I'm seeing stuff which is not in the parse value.  Why?
23:47 jeffreykegler A: Events are generated based on the parse so far.  Events will be generated for symbols that subsequent input prevents from being part of the parse.
23:48 jeffreykegler On the positive side, if what's going on in this example is completely clear to you, then congratulations!  You really understand Marpa's SLIF parse events.

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