jansheikkinen / trinic Goto Github PK

I know not how or why, but generation of the AST leaks memory according to my linter lol

The examples directory is filled with outdated representations of the language; all but one of the files have the extension .uc instead of .tc.

At the moment, a simple error like in the code rint(420). produces the following error messages:

[PARSER ERROR]: (1, 5) Expected end of statement at (
[PARSER ERROR]: (1, 5) Expected expression at token (
[PARSER ERROR]: (1, 9) Expected end of statement at INTEGER
[PARSER ERROR]: (1, 9) Expected end of statement at )
[PARSER ERROR]: (1, 9) Expected expression at token )

In the end, I'd love this error to look more like:

[ERROR] (1, 5) Undefined function 'rint':
  rint(420).
  ^^^^

My current priority is getting rid of the cascading effect caused by a single error. Five messages due to the result of a single error is unacceptable. There should be one message for every one error.
Ideally, I'd have the functions that can produce errors return some sort of Result type akin to Rust, and once a statement reaches its first error, just print that and move directly onto the next statement. It'd have to be a pretty bad error to involve more than one statement at a time, so this is generally a good way to prevent cascading errors. Obviously, if any errors are returned anywhere, execution should stop after parsing is complete. I believe that's how Crafting Interpreters did it, which I'm loosely following.

Furthermore, a lot of the current error handling was written haphazardly. In some points, I intentionally wrote the code in a way where I wouldn't have to handle any errors that arose. And a lot of the code that I did write could be extracted into a separate src/error/error.c file, and it'd be pretty nice to clean all that up.