and then call eval2 instead of eval - hopefully that won't mess you up too much (although the new eval won't have access to the variables in the current scope).
Espruino is a JavaScript interpreter for low-power Microcontrollers. This site is both a support community for Espruino and a place to share what you are working on.
Ok, it looks like this is an Espruino issue caused by
eval
messing up the parse state.It can be caused just by:
I've filed a bug for it here
To work around this for now, add:
and then call
eval2
instead ofeval
- hopefully that won't mess you up too much (although the new eval won't have access to the variables in the current scope).