@Gordon, thanks for your detailed response. I eliminated some functions and added some ifs - to de-modularize increasing dependency and tighter coupling - to get temporarily over the issue - not the preferred SW best practice. Since it is in (the infrastructure) framework, it is manageable.
When increasing application complexity without going more asynchronous, I expect it to happen again.
Is there a way to ask the Interpreter how much stack space is left and a rough/average break down into number of nested function calls?
Another question is how do fat arrow functions compare to standard functions? I know about some limitation but that may be different in the Espruino context with interpretation on the source / no byte/intermediate code.
© Espruino, powered by microcosm.
Report a problem