Post Reply 
Compensating for HP-35S’ shortcomings
01-27-2019, 09:20 PM
Post: #17
RE: Compensating for HP-35S’ shortcomings
(01-27-2019 06:55 PM)Steve Simpkin Wrote:  By having *all* available memory shared between program and data, it allows the user to choose which is more important for a specific task. (...) 11C (...) I would rather have the option to use them as I choose.
OK, but in this case you have no possibility to "choose", because the the memory is not shared as you understand and works like on 11C.
The 11C and 32SII totally different. The 32SII works like the 12C: if the program length is increase, the available memory together with the memory for variables is decreases.
What you say, to "choose how many registers I need" is available on eg. TI-59, TI-57 LCD, TI-65 or on 11C, 15C: you can set the memory partiton. But on 32SII this is not implemented.
The other side on CASIOs, where the 26 variable is always available, maybe a limitation, but the size of memory good enough (typically bigger than HPs or TIs: 4000P: 550 steps, 4500P: 1103 steps, 4800P: 4500 steps, 5800P: 28500 bytes). BTW: on CASIOs you can increase the memory for variables (DEFM).

I have a 32SII since 1998, that was my first HP, I really like it. I have one idea according to above: I never tried one basic thing on it: If I have limited memory for variables, how (i) works? Eg. I have 24 bytes for vars. I store something in B, C and D, the remaining memory is 0 and I store 1 in i, can I RCL (i)?
Find all posts by this user
Quote this message in a reply
Post Reply 

Messages In This Thread
RE: Compensating for HP-35S’ shortcomings - Csaba Tizedes - 01-27-2019 09:20 PM

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