Perl 6 - the future is here, just unevenly distributed

IRC log for #marpa, 2015-05-28

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

All times shown according to UTC.

Time Nick Message
00:07 jeffreykegler ronsavage: re http://irclog.perlgeek.de/marpa/2015-05-27#i_10663953
00:08 jeffreykegler Public release (as I see it) comes after 4.) -- Porting the Marpa::R2 test suite.
00:16 ronsavage jk: Sounds good to me.
01:36 ronsavage joined #marpa
01:54 ronsavage joined #marpa
02:04 ronsavage joined #marpa
03:30 ronsavage joined #marpa
03:50 ronsavage joined #marpa
04:00 rns joined #marpa
04:13 rns jeffreykegler: re http://irclog.perlgeek.de/marpa/2015-05-27#i_10663959 -- sounds good.
04:14 rns 7.), to make a good number :), would be a wrapper API (probably in C) for Perl and other languages.
06:54 lwa joined #marpa
14:35 koo6 joined #marpa
15:29 jeffreykegler joined #marpa
15:29 jeffreykegler https://www.youtube.com/watch?v=9Dc9Btro4xc
15:30 jeffreykegler Ruslan Zakirov's talk on the Marpa parser, from YAPC::Russia 2015
15:40 jeffreykegler I note Ruslan Z. describes LATM as "Longest *Expected* Token Match", which mgith be a better term for it.
15:40 jeffreykegler My vocabulary is (as you'd imagine) heavily influenced by the academic literature, ...
15:40 jeffreykegler and recognizers "accept" things, ...
15:41 jeffreykegler which is why "Longest *Acceptable* Token Match" is the phrase that occurred to me.
19:04 lwa joined #marpa
20:01 koo6 joined #marpa
21:43 jeffreykegler joined #marpa
22:47 ronsavage joined #marpa
22:50 ronsavage jk: Re Expected 'v' Acceptable. To me, the latter is much to be preferred. I expect all sorts of tokens at a given point, and the only one acceptable at that point is the longest. I fell sure that sort of thinking is what guided the original adoption of Acceptable.

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