Lenny,

>What if the lengths of str1 and str2 are not known? How do you then get
>access to num1 and num2(and str2). In some, if not most cases, using
fixed
>legnth records would be a waste of valuable space on the Palm. ie.
Using 50
>bytes to hold only 5+1(NULL) = 6 of my name "Lenny\0".
>
>I need to do this in my recordPack/Unpack procedures, and I am trying
to
>save space by not using fixed length records.

Use variable records.  Why not just add a length attribute to your
record which will tell you how long your variable length field is?  If
it won't ever be more than 255 bytes in length (which is what I gathered
from your message), then a byte is plenty of storage space for you and
not a lot of overhead for each individual record.

Cheers,

Mike

Reply via email to