We need to override location settings for tokenizer and parser for the intake_c that eval is using.
Perhaps add a function on intake_c that says "eval_override" and give it a start locator for error reporting. That way the user can actually see where the error is
%_cb is evaluated to nil so this was programmer error as nil is not a function or a symbol, but nil literally, but the error was :
Message: Invalid instruction list - Expected symbol, access list, or instruction list
with some random ass locator.
This relates to eval as the body of a macro is stringed and then, when called, executed via eval
We need the locators generated to offset correctly to index into where the macro is defined, or utilized. It just needs to make sense and help the user understand what went down. right now its the wild west when this occurs.
Errors from
eval
command are bad.We need to override location settings for tokenizer and parser for the
intake_c
that eval is using.Perhaps add a function on intake_c that says "eval_override" and give it a start locator for error reporting. That way the user can actually see where the error is
I found this out wth:
%_cb
is evaluated tonil
so this was programmer error asnil
is not a function or a symbol, butnil
literally, but the error was :Message: Invalid instruction list - Expected symbol, access list, or instruction list
with some random ass locator.
This relates to
eval
as the body of a macro is stringed and then, when called, executed viaeval
We need the locators generated to offset correctly to index into where the macro is defined, or utilized. It just needs to make sense and help the user understand what went down. right now its the wild west when this occurs.