...this is due how the Espruino JavaScript interpreter works: every time a JavaScript expression completes - in level 0 - on upload, it is executed and the source string is released and interpretation resources are freed up for next expression. ...just a reasonable guess.
The way I emulated the upload is what actually happens on upload, which is not in level 0, where as @AkosLukacs did it, it is in level 0. In other words, it is a way to overcome temp memory issues... this is another reason why @Gordon's Espruino JavaScript interpreter interprets from source and not from some byte code to deliver this high-level environment in a memory resource constraint setting, as all the power-frugal mc are.
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.
...this is due how the Espruino JavaScript interpreter works: every time a JavaScript expression completes - in level 0 - on upload, it is executed and the source string is released and interpretation resources are freed up for next expression. ...just a reasonable guess.
The way I emulated the upload is what actually happens on upload, which is not in level 0, where as @AkosLukacs did it, it is in level 0. In other words, it is a way to overcome temp memory issues... this is another reason why @Gordon's Espruino JavaScript interpreter interprets from source and not from some byte code to deliver this high-level environment in a memory resource constraint setting, as all the power-frugal mc are.