OK. Now I understand. The $slr->ambiguous() method, in producing its
diagnosis of the ambiguity, is assuming you'll treat an ambiguity as a
fatal error, and won't go on to call value(). At the very least, I
should document this. -- jeffrey
On 09/30/2014 10:22 PM, Ruslan Shvedov wrote:
I've added a couple of series_restart() calls to your gist, see
https://gist.github.com/rns/0371dfcffa6887f4e5a2 to avoid exceptions.
The test output makes is arguably more useful that way.
On Wed, Oct 1, 2014 at 8:01 AM, Ron Savage <[email protected]
<mailto:[email protected]>> wrote:
I've switched over to gists because they allow comments:
https://gist.github.com/ronsavage/a372ca2802f47808374b
As for desired behaviour, you'll note cases 0 & 4 print "Output:
!->! OK count: 2." This means the parse is correct, which is true.
So why don't all cases do that?
I accept there could be errors after calling value() [that's why I
always save the value], but I was expecting the above to be
printed in all cases, whether or not the parse is ambiguous.
--
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]
<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.
