Inteteresting.... On Wed, Jun 10, 2015 at 9:36 AM, Camille <camille.ter...@gmail.com> wrote:
> Hello Pharoers and Moosers, > > I did a Pratt parser extension for PetitParser. > > <snip> > @PP Devs: > I had trouble with the PPContext furthestFailure that is taken into > account instead of the failures I return, so I had to redefine > #parseWithContext: to return the failures I want. The results given by > furthestFailure were not very meaningful in my case (the same is true for > PPExpressionParser btw). > But I guess it was introduced because it gives good results in other > cases. > So would it be possible to change this behavior to let the parser decide > if it returns the furthestFailure or the original failure? > The intent behind the furthestFailure is that it give the failure that gets the furthest into the source stream. It is most useful when there are embedded choice operators in the parser - the original/pre furthest behaviour would return the last failure, which depending on the incoming stream and the order of the choice options could be significantly not useful. I ran into this when working with the sql parser, which started off with the outer choice of (by memory): ^ selectStatement / insertStatement / updateStatement / deleteStatement If I was trying to part a select statement that had an error at the very end of the statement, the parser would return an error talking about how the incoming stream failed in deleteStatement. Not useful. I would be saddened if this further failure was not available. -cbc
