Poll: What should happen with LIST-> when an overflow happens?
It should not give the LIST-> if an overflow will happen
It should warn the user, then do it
It should just overflow off the top
Something else
[Show Results]
Note: This is a public poll, other users will be able to see what you voted for.
Post Reply 
What to do with stack overflow OBJ->/LIST->?
06-22-2016, 05:02 AM
Post: #8
RE: What to do with stack overflow OBJ->/LIST->?

?? 128 stack size limit ??

Yes, there is a reason...

The HP 39GII had a very limited memory, and, a recurring problem of the HP39G+/HP40G was customer complaining of out of memory condition caused by the fact that they had thousands of objects on the stack.

So, when the 39GII was created, we simply pre-allocated 128 stack levels for input/outputs. It made sense there.

When Prime came along and we added RPN, the same 128 stack structure was kept (made thing easier/faster)... At the time, we designed RPN as an entry system, not a programming one, therefore thinking that 128 stack levels ought to be enough for everyone...

And here you have it. This is the reason. This is not an excuse, nor a justification, it is just... the reason...



Although I work for the HP calculator group, the views and opinions I post here are my own. I do not speak for HP.
Find all posts by this user
Quote this message in a reply
Post Reply 

Messages In This Thread
RE: What to do with stack overflow OBJ->/LIST->? - cyrille de brébisson - 06-22-2016 05:02 AM

User(s) browsing this thread: 1 Guest(s)