Perl 6 - the future is here, just unevenly distributed

IRC log for #marpa, 2017-07-30

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

All times shown according to UTC.

Time Nick Message
00:11 kook_ joined #marpa
00:48 Cheery joined #marpa
00:51 deep-book-gk_ joined #marpa
00:52 deep-book-gk_ left #marpa
01:52 ilbot3 joined #marpa
01:52 Topic for #marpa is now Start here: http://savage.net.au/Marpa.html - Code paste/run: https://f.perlbot.pl/#marpa - Jeffrey's Marpa site: http://jeffreykegler.github.io/Marpa-web-site/ - IRC log: http://irclog.perlgeek.de/marpa/today - Youtube channel: https://www.youtube.com/channel/UCYKVfGBtfTqbs1JdYq-dc5g
05:18 ilbot3 joined #marpa
05:18 Topic for #marpa is now Start here: http://savage.net.au/Marpa.html - Code paste/run: https://f.perlbot.pl/#marpa - Jeffrey's Marpa site: http://jeffreykegler.github.io/Marpa-web-site/ - IRC log: http://irclog.perlgeek.de/marpa/today - Youtube channel: https://www.youtube.com/channel/UCYKVfGBtfTqbs1JdYq-dc5g
05:40 ronsavage joined #marpa
05:43 ronsavage JK: Re Marpa-R3/pod/Event.pod. The 2 types of events, Exhaustion and Rejection, don't say if they are lexeme or non-lexeme events. I think it would be good if this could be spelled out, even if they are both the latter type.
05:46 ronsavage Under the heading 'Ambiguity', this sentence ' In the example, events for both the symbols <ambig1> and <ambig2>, as well as all their derived symbols, trigger.' contains a link which goes nowhere.
05:49 ronsavage Under the heading 'Location events', this sentence 'It is declared using the appropriate named argument of the recognizer's new() constructor.' contains a link to the correct doc, but in that doc the text 'location event' does not appear. So how do we declare location events, or does some form of elsewhere documented event declaration make some events location events?
05:54 ronsavage Under the heading 'Ambiguity', this sentence 'If a parse is ambiguous, events trigger for all the possible symbols.' makes me think that in order to differentiate between events in an ambiguous context (I guess assuming I have 1 default handler), I have to compare the block offset and lexeme offset at each events' triggering, and if they match the previous trigger's values, then I have ambiguity. The reason I ask is that my demo just push
05:55 ronsavage Or should I stick with 'my $status = $self -> recce -> ambiguous' after parsing finishes, to check ambiguity?
05:59 ronsavage Re location events: I see now returning toward the top of the doc, to the heading 'The life cycle of events', makes things clearer.
06:24 ronsavage And, does this summary make sense: http://savage.net.au/Marpa/html/Marpa.R3.Event.Types.html
07:23 ronsavage joined #marpa
07:33 kaare__ joined #marpa
07:41 kaare__ joined #marpa
08:45 sirdancealot joined #marpa
12:31 kaare__ joined #marpa
15:26 hobbs joined #marpa
15:26 hobbs joined #marpa
17:24 idiosyncrat joined #marpa
17:25 idiosyncrat ronsavage: re https://irclog.perlgeek.de/marpa/2017-07-30#i_14941973 -- thanks for the input.
17:57 idiosyncrat ronsavage: re https://irclog.perlgeek.de/marpa/2017-07-30#i_14941993 -- that link works for me, at least it does so in the github repo.
18:05 idiosyncrat ronsavage: re https://irclog.perlgeek.de/marpa/2017-07-30#i_14942002 -- in the latest commit, I've clarified that sentence.
18:06 idiosyncrat I've also commit some changes which reorganize the discussion of event types, for clarity
18:08 idiosyncrat ronsavage: re https://irclog.perlgeek.de/marpa/2017-07-30#i_14942021 -- events really aren't adequate for catching and describing ambiguities -- that's why I created the ASF's, which the $recce->ambiguous() method uses.
18:09 idiosyncrat ronsavage: re http://savage.net.au/Marpa/html/Marpa.R3.Event.Types.html
18:09 idiosyncrat That's a really great table.
18:10 idiosyncrat Re the two ?'s, they should be blank.  "Location event" and "instance event" are mutually exclusive.
18:15 idiosyncrat ronsavage: re https://irclog.perlgeek.de/marpa/2017-07-30#i_14941973
18:16 idiosyncrat In the latest commit, I clarify that exhaustion and rejection events are location events.  Lexeme and non-lexeme events are subtypes of instance events.  Hopefully these rewrites make that clearer.
18:17 idiosyncrat ronsavage: Thanks for spotting these!
22:31 ronsavage joined #marpa
22:32 ronsavage JK: Re https://irclog.perlgeek.de/marpa/2017-07-30#i_14943489. Ahh. But not on CPAN, which is what I'm looking at. So, OK.
22:45 ronsavage I've re-arrange the table, and it's clearer now: http://savage.net.au/Marpa/html/Marpa.R3.Event.Types.html.
22:46 ronsavage Re https://irclog.perlgeek.de/marpa/2017-07-30#i_14943513. Yes, I thought so, but I put something concrete there to get a vote from you :-).
23:07 ronsavage And I've added there Marpa::R2 DSL table to the R2 FAQ and the Marpa::R3 Event table to the R3 FAQ.
23:16 ronsavage Re: https://irclog.perlgeek.de/marpa/2017-07-30#i_14944286. For those not familiar with the 'Marpa DSL table', it's Q 148, which points to http://savage.net.au/Marpa/html/Marpa.R2.DSL.Structure.html.

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