Go through parser and make sure it deals better with invalid code #98
Labels
good first issue
Issues that are clearly defined and don't require a deep understanding of Stacksmith internals.
interpreter
Hammer programming language: Parser, tokenizer, interpreter.
Now that we actually run our parser over the script for formatting, make sure that the parse tree when errors happen is always left in a state that calling GenerateCode() on it doesn't crash.
I've fixed a bunch of cases where a command used to be able to just assume it had 2 arguments by the time GenerateCode was called, but now with runtime-deferred errors and the formatter walking the parse tree, we need to add extra NULL checks and extra error checks before so we are not dumb and set an argument to NULL.
The text was updated successfully, but these errors were encountered: