I don't think you should assume I have a *good* reason for using yacc
over brag. I just thought that in my case it would be easier to put some
code in the productions rather than build a full parse tree and then
process that. I seem to have been wrong about that. I will take another
look at bra
`br-parser-tools` has some patches needed to make `brag` work, e.g., using the
srcloc structure. I forked rather than patch the underlying `parser-tools`
package because I didn't want to destroy the fragile ancient artifact. I fixed
a few bugs; the others persist. I notice, for example, that you
Thanks for confirming. I had actually started with the lexer-src-pos version
but had other problems like exn:fail:read wanting a list of srclocs and the
lexer only having positions. So I switched to lexer-srcpos which fixed the
exception but broke the parse. Maybe I should do a conversion betwee
On Mon, Jun 8, 2020 at 8:36 PM jon stenerson wrote:
>
> Hi all,
>
> I don't understand the error message here. The parser seems to be
> looking for a position-token but the lexer is sending srcloc-tokens? Is
> there a simple fix? Using Racket 7.7 on WIn 10.
Hi Jon,
Yes, you're right, and there i
Hi all,
I don't understand the error message here. The parser seems to be
looking for a position-token but the lexer is sending srcloc-tokens? Is
there a simple fix? Using Racket 7.7 on WIn 10.
I am also confused about whether to use br-parser-tools or parser-tools
package. br-* is the more
5 matches
Mail list logo
