-
Notifications
You must be signed in to change notification settings - Fork 20
Better error reporting #52
Copy link
Copy link
Open
Description
Various methods for catching errors exist in compilers. Document best approaches for doing so in this issue and tackle the following problems in error reporting:
- Print location of statement before outputting any statement.
- Print location of line number where a compile error happened to STDOUT.
- Research and setup various error classes that can arise out of a badly written program and how they should be reported.
Errors to handle:
- Proper declaration of required functions in attached classes.
- Error if attached classes are being used and
rubex/rubyis not required usinglib.
Reactions are currently unavailable