Skip to content

Better Script parsing messages #2

Description

@FlamerShaftglutton

Issue:

Testing scripts with the test program is a bit of a pain, but is doable. However, debug messages (especially for getting and setting variables) are often vague or nonexistent when something breaks. This makes debugging scripts challenging.

Workarounds:

Use the test program and use trial and error to determine what's wrong with your script.

Suggested Solution:

Implement or improve debugging messages for the functions, especially the get and set functions. Possibly add another compiler flag like -DSCRIPTMESSAGES that allows for extremely detailed output of what exactly the interpreter is parsing the script as.

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions