Tracker: Bugs
5
Human Readable Errors - ID: 490984
Last Update: Tracker Item Submitted ( gazook )
Currently the text associated with the oclError parse
tree nodes is the bison generated error message, which
is pretty nasty: including but not limited to
references to the parser token names.
Find a way to setup error messages that are actually
helpful to the user. At the very least, the line and
column number when the parsing went to hell in a
handbasket should be included in the error text.
Jude Nagurney
parsing
None
Public
