Jeremy Leach
Senior Member
Hi, just an interesting and a bit puzzling observation. I've been playing around a lot with long lookup commands. I've just noticed that for a lookup command containing strings :
String of 1 byte takes up 10 program space bytes.
String of 238 bytes (what my program uses) takes up 367 bytes. ie 129 extra bytes on top of the string itself !!! I'd be interested in an explanation of what appears to be a huge overhead in code storage space.
I'd become really keen on the Lookup command until I noticed this ;-)
I'm looking for ways to save program space now, so am now going to use the data storage space instead and write my own lookup subroutine, which I expect will execute slower.
Edited by - jeremy leach on 4/12/2005 3:03:57 PM
String of 1 byte takes up 10 program space bytes.
String of 238 bytes (what my program uses) takes up 367 bytes. ie 129 extra bytes on top of the string itself !!! I'd be interested in an explanation of what appears to be a huge overhead in code storage space.
I'd become really keen on the Lookup command until I noticed this ;-)
I'm looking for ways to save program space now, so am now going to use the data storage space instead and write my own lookup subroutine, which I expect will execute slower.
Edited by - jeremy leach on 4/12/2005 3:03:57 PM