Perl 6 - the future is here, just unevenly distributed

IRC log for #marpa, 2017-06-13

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

All times shown according to UTC.

Time Nick Message
00:27 idiosyncrat joined #marpa
00:28 idiosyncrat Demat!
01:48 ilbot3 joined #marpa
01:48 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
02:45 idiosyncrat It took a while, but I'm finally getting the new event mechanism to pass a couple of the tests in the test suite.
02:46 idiosyncrat Good news is that the $slr->resume and $slr->read interface remains and, unless it gets in the way of something, won't be removed in the next Marpa::R3 release.
02:46 idiosyncrat Bad news is that anything that uses events will have to change from the event-driven IF to a new callback IF.
03:19 ronsavage JK: I was wondering where you'd vanished to.
03:21 idiosyncrat I might take a break from Marpa at some point someday, but I've been immersed in the Marpa::R3 recognizer.
04:14 ronsavage Don't take a break before you rename it to Kollos!
06:19 kaare__ joined #marpa
07:11 sirdancealot joined #marpa
11:56 Cheery I know that marpa eliminates null transitions because they are troublesome.
11:57 Cheery but recently I've wondered about extending my parser to support non-linear parsing.
11:58 Cheery shifting from multiple sources and merging the result is simple.
12:01 Cheery but lets say I wanted to copy a state and continue from there..
12:02 Cheery it becomes shift, reduce, copy state, shift, reduce
12:02 Cheery and I remember  reading somewhere that the shifts must come first in marpa.
16:11 sirdancealot joined #marpa
18:03 idiosyncrat Cheery: Yes, Marpa rewrites null productions before running its parse engine, so that the parse engine itself does not have to deal with them.  But their effect is still there.
18:04 idiosyncrat I'm not sure how that connects with "non-linear parsing" or in which sense you mean that.
18:05 idiosyncrat Also, Marpa is not a shift-reduce parser in the standard sense of those terms.
18:09 black_ant joined #marpa
18:09 idiosyncrat ronsavage: re https://irclog.perlgeek.de/marpa/2017-06-13#i_14724005 -- I meant a short break.  And why the time pressure on the Kollos rename?
18:41 Cheery idiosyncrat: I like to think of it in those terms.
18:41 Cheery http://leverlanguage.com/doc/latest/chartparser.html
23:20 ronsavage joined #marpa
23:24 ronsavage JK: There's no real pressure on renaming to Kollos. I just keep thinking of Neil's comments about PAUSE admins rethinking my usage of Kollos if we don't utilize the namespace within 1 year. Plenty of time yet :-).
23:29 idiosyncrat joined #marpa
23:36 idiosyncrat ronsavage: re https://irclog.perlgeek.de/marpa/2017-06-13#i_14729030 -- We may want to ping them in a year, with an update on Kollos.  When I started a lot of people thought Marpa was a waste of CPAN space, and a handful were been willing to say so on the record.  But I think at this point we can be confident that our case will receive the kind of consideration it merits.

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