rubex icon indicating copy to clipboard operation
rubex copied to clipboard

Better error reporting

Open v0dro opened this issue 7 years ago • 1 comments

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/ruby is not required using lib.

v0dro avatar Mar 30 '18 01:03 v0dro

Preliminary resources:

  • https://www.obj-sys.com/docs/acv62/CCppHTML/ch02s06.html
  • https://softwareengineering.stackexchange.com/questions/39700/how-should-compilers-report-errors-and-warnings
  • https://en.wikibooks.org/wiki/Compiler_Construction/Dealing_with_errors

v0dro avatar May 02 '18 13:05 v0dro