unread
From a completely separate stand point. The ability to customise what token names show up as in an error seems like a much better solution
--
James Butler
Sent from my iPhone
lemon would indeed get rid of actual "names" for such tokens, and would
rather display "unnexpected ::".The problem with lemon is that it turns out to still be a tad bit slower
than yacc, with some complications on the grammar side (the compiler
helper functions were made for yacc). So unless there is a major speedup
breakthrough, it won't happen in a near future, sadly.So does that leave us back to square 1 with replacing the token name? Or
is there another way that error messages can be tweaked to not show
actual token names?