So, we talked about this a bunch internally. And Bob gave much (most?) of
this answer, but just for the record...
The basic answer is that given the current (internal and subject to change)
implementation of the Data Manager, a heap can't be larger than 16
megabytes. So we would have to have two heaps if we were to ship a 32
megabyte device without first changing some of the internal structures of
the Data Manager (a simple matter of programming, as they say.)
So the question is, given the assumption that there'd be a Palm OS device
with more than 32 megabytes of directly accessible ram, would it be before
or after we change the Data Manager's internal code? (While keeping the
APIs the same, one would assume.) The OS team wasn't willing to guarantee
that such a device would not ship from us or a licensee without first
changing the OS code.
So the answer is no, don't make that assumption that there'll only be one
storage heap forever and ever. DmResizeRecord might return a different
handle than the one it was given.
-David Fedor
Palm Developer Support
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palm.com/devzone/mailinglists.html
