Open areidmeyer opened 4 years ago
This is actually part of the bison grammar recognition, not part of the semantics glslang implements and has full control over.
It used to say just "syntax error", and not give any clues at all. By adding %define parse.error verbose
we get more.
If there are ideas how to improve this, please contribute.
Currently, if I make this sort of mistake, I get this sort of error:
This example is oversimplified, for more complex cases it would be really useful if it could include the IDENTIFIER it couldn't resolve in the error. Something like:
In particular, the post preprocessor identifier is helpful here for debugging.