So it's a regression? That puts a different light on the matter.
With regressions, sometimes I'll decide that the application was
depending on undocumented behavior, which was at its own risk, and that
the regression is not a problem. But in dubious cases, the benefit of
the doubt should go to the application. Another argument for supporting
this undocumented behavior is that there's no downside -- I'm sure
nobody wrote an application that relies on its named argument hashes
getting changed by the Marpa methods. :-)
I'm putting this release candidate on hold, while I research this one
and think it out. The SLIF constructor's argument handling could use
some refactoring anyway.
-- jeffrey
On 12/21/2013 03:50 PM, Ron Savage wrote:
Runs OK with V 2.077001. Fails under 2.077_013:
ron@zigzag:~/perl.modules/Genealogy-Gedcom$ a.pl
Call 1
Call 2
'grammar' name argument to scanless_r->new() is undefined
It should be a ref to Marpa::R2::Scanless::G
Marpa::R2 exception at /home/ron/bin/a.pl line 10.
But, did you really intend to address this to me :-)?
--
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 marpa-parser+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
--
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 marpa-parser+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
