[racket-dev] Need a good way to fix location on cfg-parser

From: Danny Yoo (dyoo at hashcollision.org)
Date: Fri Jan 4 19:46:39 EST 2013

I've caught a bug with regards to the source locations constructed by
cfg-parser, but I don't know quite what the right patch is.  I do know
what the _wrong_ patch is, so maybe that will help?  :)

Here's what I've kludged so far:


The main problem is that a non-primitive pattern may consist of
multiple tokens, so it's not correct to just look at one of them when
constructing the position.  I kludged it so "parse-and" keeps a hold
of the positions before and after parsing the first "rule-a", and
passes the positions along to the success continuation.

Posted on the dev mailing list.