Skip to content

Better error reporting #52

Description

@v0dro

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.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions