Post Reply 
41CL Maximum registers for DATA/PROGS storage
07-25-2018, 05:07 PM
Post: #21
RE: 41CL Maximum registers for DATA/PROGS storage
(07-25-2018 12:09 PM)Ángel Martin Wrote:  
(07-20-2018 06:22 AM)Podalirius Wrote:  I readed Cl XPMEM manual: seems that the commands for use of the additional 1024 registers are more byte consuming.

Looks like this thread is more about the RAMBOX but just for completion sake - yes, using the Expanded register functions (YSTO, YRCL, etc...) has a more demanding byte consumption. However you have more standard memory for your program code - since no standard DATA registers are needed.
Answer coming from the creator of the module ... what can you ask more. Smile
I had not seen the implied question and thus never answered it.
Thank you Àngel.
Sylvain
Find all posts by this user
Quote this message in a reply
07-25-2018, 06:47 PM (This post was last modified: 07-25-2018 06:48 PM by Ángel Martin.)
Post: #22
RE: 41CL Maximum registers for DATA/PROGS storage
(07-25-2018 04:43 PM)Gene Wrote:  ...and since a very likely use of the Y-registers is by way of indirect addressing, the byte usage probably will not be as high as the savings in regular data registers would use.

Tough to do a determinant of a 20x20 matrix any other way. :-)

Very true indeed, thanks for pointing it out!

BTW the registers directly accessible by YSTO, YRCL... are limited by the standard prompt field, of three characters - from 000 to 999. Using EEX opens up a fourth field with a leading "1", thus up to 1999 max. So the current 1,024 could be upped to 2,048 (or even 3,096) like it is the case with the SandMatrix 4Y - where the registers are managed by the matrix functions instead...

Cheers,
ÁM

"To live or die by your own sword one must first learn to wield it aptly."
Find all posts by this user
Quote this message in a reply
Post Reply 




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