As I've just said on the IRC channel, Ron is absolutely right -- he tried to point this issue out to me earlier, but then it was entangled with another one -- other modules like Moo which treat the global symbol tables as if they were part of the module internals.
I intended Marpa's use of the symbol tables as unproblematic, and assumed that it was, but unknown to me Marpa::R2 had a bug which made it "look for trouble". latk reproduced this problem in a Moo-free way. So my apologies to Ron for not thinking his reports through more deeply at that time. On Wed, May 6, 2015 at 7:53 PM, Ruslan Shvedov <[email protected]> wrote: > Actually, latk++ is planning a pull request to Marpa Papers about this -- > https://github.com/jeffreykegler/Marpa--R2/issues/254#issuecomment-99229630 > > On Thu, May 7, 2015 at 5:48 AM, Ron Savage <[email protected]> wrote: > >> I'm delighted to see latk has investigated this thoroughly, and we have a >> fix. >> >> I had problems with this 2 or 3 years ago, and documented it in >> http://savage.net.au/Perl-modules/html/marpa.papers/chapter3.html. >> Search that page for Moo. >> >> -- >> You received this message because you are subscribed to the Google Groups >> "marpa parser" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> For more options, visit https://groups.google.com/d/optout. >> > > -- > You received this message because you are subscribed to the Google Groups > "marpa parser" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "marpa parser" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
