Both WP 31S and WP 34S manuals now available for individual POD

[Bit]

(02-22-2015 04:45 PM)walter b Wrote:  Well, as you wrote:

Quote:stack is always saved (may use a lot of memory)

(emphasis added).

Those who use nested functions of this kind should know what they are doing. And they can control it by setting stack size as they need it. OTOH, destroying seven stack levels just for nothing doesn't look like a reasonable alternative IMHO.

Even saving a 4-level stack could use a lot of memory in nested calls and that would make the 34S less capable. Perhaps a secondary set of opcodes, that don't save the stack, could be provided as a fourth option.