In support of the 33s & 35s
|
01-04-2018, 07:31 PM
Post: #49
|
|||
|
|||
RE: In support of the 33s & 35s
(01-04-2018 07:00 PM)Dieter Wrote: First of all, I think I was wrong about the memory usage of numeric constants. My knowledge essentially was what BartDB said: any numeric constant takes 37 bytes. But I think this is wrong and the 37 bytes refer to the memory used by the data registers, including the 800 indirect ones on the 35s. For numbers in programs it looks like it's actually 3 bytes plus one more byte for each digit / decimal point / E / sign. So a simple "3" requires four bytes. Regular 33s/35s commands occupy 3 bytes, so "pi IP" is 6 bytes, i.e. two bytes more than a plain 3. In actual fact it is difficult to determine the memory usage of anything on this calculator. With a cleared calculator: MEM shows 30,192 bytes available add LBL A MEM shows 30,189 bytes available, i.e. a line with a LBL uses 3 bytes add A002 3 MEM shows 30,151 bytes available, i.e. adding line with a constant takes 38 bytes But with a calculator with 2 small programs and a few equations in it: MEM shows 29,482 bytes available add LBL X (because A is already in use) MEM shows 29,482 bytes available, so now a line with a LBL uses 0 bytes? add X002 3 MEM shows 29,447 bytes available, so now adding line with a constant takes 35 bytes? Confusing. The only thing we can be sure about is the speed advantage, as this is measured with a device that's not part of the calculator. |
|||
« Next Oldest | Next Newest »
|
User(s) browsing this thread: 9 Guest(s)