I am using Happy to generate a parser.
I have found that when I give it tokens which match part of the grammar at a lower level than the top level (such as giving it an expression on it's own, that isn't part of a statement), I get an "Internal Happy Error" rather than a parse error.
Is there a way to override notHappyAtAll
so that I can print a better error message than "Internal Happy Error"? Obviously other than changing the auto-generated parser file as I'd have to do it every time I updated the grammar.
%error { parseError }
-parseError
is some user defined function. See Chapter2 of the manual. – UnpracticalnotHappyAtAll
:/ – HydrometallurgynotHappyAtAll
is a brilliant name for a function. – Barger