HP-35s Memory Management

[Matt Agajanian]

Hello all.

Yes, my joy for RPN and programming has enticed me to buy both the 33s and 35s when they were first out of HP's factory.

Even though these two have their faults like San Andreas, perhaps they're not as much the bastard children of the HP family.

There is a peculiar structure that I'm even perplexed as to say "What were they (HP) thinking." And it's the memory register structure of the 35S. I can see that registers A-Z, like the alphabet, can be addressed by a simple A, B, C keystroke, but why did the classic 00-800 register addressing be convoluted to both an indirect addressing scheme plus on the less than zero number scale.

The way I see it, which makes much more logical sense registers 00 to 800 could have been addressed in the conventional manner with A-Z registers being designated the negative number addressing.

Two simple solutions comes to mind:
Variables/registers A-Z could have been addressed with a preceding decimal point or CHS stroke for example as [STO] [ . ] A...Z or [STO] [CHS] A...Z. leaving access to registers 0 to 800 with conventional register addressing.

For indirect addressing, to retain conventional methods, if the I or J register contained a positive value, as usual, registers 0-800 could be accessed.

To accessss variables indirectly, -1...-26 in the I or J register would access variables A...Z.

I preface with these to pose my major curiosity.

Granteed porting over Classic, Woodstocks, Voyageres, etc. calcs only needs access to 25 or less registers (except the 29C with 30 registers), what technique have you used when porting indirect register addressing portions of code to the 35S?

Thanks