Perl 6 - the future is here, just unevenly distributed

IRC log for #marpa, 2017-06-20

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

All times shown according to UTC.

Time Nick Message
00:13 Cheery_ joined #marpa
00:14 lucs_ joined #marpa
00:14 sivoais joined #marpa
00:17 perlbot joined #marpa
00:20 btyler joined #marpa
00:24 ronsavage joined #marpa
00:24 hobbs joined #marpa
00:24 sivoais_ joined #marpa
00:34 sivoais joined #marpa
00:49 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
07:12 ronsavage joined #marpa
10:22 Cheery joined #marpa
10:30 Cheery joined #marpa
10:31 Cheery joined #marpa
15:45 sirdancealot joined #marpa
15:52 sirdancealot joined #marpa
18:25 idiosyncrat I just uploaded Marpa-R3-4.001_047
18:27 idiosyncrat The has a new feature -- Perl callbacks for event handling.  Currently both callbacks and the previous mechanism (using the $slr->events() method) work -- if there is an "event_handlers" named argument, callbacks are used, otherwise the legacy $slr->events() method is used.
18:27 idiosyncrat The $slr->events() method will be eliminated in the next release.
18:28 idiosyncrat As discussed, $slg->symbol_name() is now incompatible -- its equivalent is $slg->g1_symbol_name.
18:28 idiosyncrat For consistency with this, $slg->symbol_ids() has been removed.
18:29 idiosyncrat Except for the $slg->symbol_name() incompatibility and the $slg->symbol_ids() removed I think this release is backward compatible.
18:29 idiosyncrat Testing is very much appreciated!!!
18:32 idiosyncrat To use the new events mechanism, look at the events POD: https://github.com/jeffreykegler/Marpa--R3/blob/master/cpan/pod/Event.pod
18:32 idiosyncrat It was heavily rewritten for this release.
18:33 idiosyncrat To get a quick idea of how the new events callback mechanism works, look at the Examples section of the POD: https://github.com/jeffreykegler/Marpa--R3/blob/master/cpan/pod/Event.pod#examples
18:35 idiosyncrat This is much expanded in this release, and contains 9 examples, starting from basic and moving on to examples that illustrate techniques adequate for even the most complex app requirements.
18:35 idiosyncrat Next on my agenda:
18:36 idiosyncrat The incompatibilities in this release were not desired, but are due to unfortunate planning --
18:37 idiosyncrat in preparation for more aggressive use of grammar rewrites, symbols now have external and internal forms.
18:38 idiosyncrat Actually, even in Marpa::R2, symbols had external and internal forms, but the differences were more modest, and were kludged over.
18:39 idiosyncrat In R3, I'd moved to the sharper external/internal difference, but kept the kludgey interface, which is increasing inadequate.
18:40 idiosyncrat My next task will be to make the leap to an interface that recognizes the External/internal rule/symbol IDs/names are different things.
18:41 idiosyncrat Btw, most users, once things settle, will not have to worry about the internal forms, and will be working with basically one idea of what a symbol or rule is, and what its ID and name is.
18:41 idiosyncrat That symbols and rules most apps will deal with will be the external ones.
18:46 idiosyncrat CPANtesters is OK, except for Andreas's "sad seven" -- seven tests on Andreas's platform which have consistently failed for a while.  Andreas often runs bleeding-edge tests, and I hope that'
18:46 idiosyncrat that's what these are.
18:47 idiosyncrat One side-effect of Marpa's going mainstream is that Marpa-related issues are now the focus of greater testing, and can be release blockers.
18:52 black_ant joined #marpa
20:30 idiosyncrat left #marpa
22:15 btyler joined #marpa
22:52 ronsavage joined #marpa
23:11 ronsavage JK: Re Marpa-R3-4.001_047. All tests pass here.
23:17 ronsavage JK: A typo in the Event.pod examples: 'hanlders' -> 'handlers'.
23:21 ronsavage JK: A note for very pedantic readers: In the Event.pod examples, this header 'Handlers which require local and non-local data.', unlike others, has a full-stop!
23:28 ronsavage JK: In the docs for 'Pause span', there is this sentence: 'When a lexeme event triggers, it will set the pause span to the start physical input stream location and length of the triggering lexeme.'. It reads a bit awkwardly. I wonder if 'the start' should read 'the start of the' or 'the starting'. And perhaps 'and length' could be 'and the pause length to the length'.

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