Improve parser error messages
Registered by
Eike
The current error messages from the parser are quite bad. The location they point to is often right, but themselves are bad.
This blueprint should collect ideas for improvement, and areas where improvement is necessary.
Blueprint information
- Status:
- Not started
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- None
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- New
- Series goal:
- None
- Implementation:
- Unknown
- Milestone target:
- None
- Started by
- Completed by
Related branches
Sprints
Whiteboard
Areas for improvement
- Quoted string
good error message for missing 2nd quote in single line string
- Unknown/misspelled keyword
- Error in expression
The error message is often "expecting end of line" Bug #602847
(?)