You are reading a single comment by @Gordon and its replies.
Click here to read the full conversation.
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.
@Gordon
Hmm, it's a difficult one - the whole queue was built around the interrupt-based comms.
To be honest on ESP8266 we still have the problem of any function that takes too long to execute causing a reset... Refactoring every function that outputs a lot of text to avoid it seems like it'd be amazingly painful, and still doesn't solve that problem.
I think at some point we'd talked about buffering to JsVars, but especially in jsvTrace that won't work, because it's expecting that the variables it's looking at won't be changing!
At one point there was talk of suspendable threads - @Kolban posted up some code (maybe for FreeRTOS?) that seemed like it would be pretty easy to integrate, and that would basically solve everything?
The only problem would be the RAM usage required to keep a separate stack for Espruino. I don't know whether it's realistic from that point of view?