Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Better error reporting #52

Open
5 tasks
v0dro opened this issue Mar 30, 2018 · 1 comment
Open
5 tasks

Better error reporting #52

v0dro opened this issue Mar 30, 2018 · 1 comment

Comments

@v0dro
Copy link
Member

v0dro commented Mar 30, 2018

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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant