No, ambiguity is *not* always a fatal error. I'll have to update the docs to warn the reader that when it is not, and when the ambiguous() method detects ambiguity, the application will need to series_restart() before calling value().

-- jeffrey

On 09/30/2014 10:56 PM, Ron Savage wrote:
Is ambiguity always a fatal error?

I realize the libmarpa does not force that, but are you saying the user should automatically assume that's the case?

--
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] <mailto:[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.

Reply via email to