> I must be missing something. If you have the address of the first
> string in the list (for the tAIS case), that gives you the address of
> the chunk. If you've got the address of the first indexed string in a
> tSTL resource, and you control the contents of the resource (e.g. the
> prefix is always an empty string), then why can't you just subtract
> three from the address, thus skipping over the length count and the
> null byte in the prefix?
That's how I'm handling it for the time being, but it's not a "SAFE" way.
The "you control the contents of the resource (e.g. the prefix is always an
empty string)" is valid for now, because I control the definition and
maintenance activities. That won't always be true. Somebody else could use
that prefix for another function later on, and consequently screw up all the
routines that count on it being empty.
There's ALWAYS a way to get there from here. Having to re-work existing
routines is what's pi$$ing me off.
Palm knows where the chunks are, and what their boundaries are. How about
providing a function to return the chunk's Ptr from an address I *do* have
available Piece of cake.
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
