You could start by adding a short information to the Marpa::* modules that
you recommend to use Marpa::R2.
I just recently started using Marpa::R2 and it was only coincidence that I
started with the new one.
Am Montag, 3. November 2014 18:51:43 UTC+1 schrieb Jeffrey Kegler:
I'm thinking of
Say I want a program to provide an option for a user to abort the run if an
ambiguous grammar is detected.
Should I test the return of just 1 of the above methods in preference to
the other? If so, which?
I'm also thinking of whether it makes sense to report something to the user
after
Just note that having an ambiguity metric does not mean that values() are
different.
Nevertheless, you know that I love non-ambiguous grammars -;
Le mercredi 5 novembre 2014 22:41:08 UTC+1, Ron Savage a écrit :
Say I want a program to provide an option for a user to abort the run if
an
$recce-ambiguous() calls $recce-ambiguity_metric() internally. Usually
you'll only need to call one of them. In your case, guessing the intent,
you only want to call ambiguous(), and if you want to do nothing for an
unambiguous parse, check for the empty string.
On Wed, Nov 5, 2014 at 2:24 PM,
Enlightenment!
--
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
