With all the different limitations on allocating memory, including the size of the dynamic heap, and the maximum size of an allocated chunk, it is not surprising that techniques to get around these problems would be useful. Since helpful is what we aim to be, we provide a couple of ways around these limitations.
If you need to allocate a 50K chunk of memory (for a buffer,
perhaps), you won’t be able to use the dynamic heap. At least
not if you’d like to be able to run on all device/OS releases.
What you can do, however, is allocate a chunk of memory from the
instead. The Data Manager call
will allocate a relocatable chunk of memory
in the storage heap that is not attached to any database. Like all
chunks in the storage heap, it’s directly addressable in
memory. Thus, you can read it just as if it were in the dynamic heap.
That is, after locking it, of course. To write to the chunk,
you’d need to use one of the Data Manager calls
DmStrCopy (see Chapter 9).
DmNewHandle restricts allocations to slightly
less than 64 KB.
When you are through with the chunk, you can free the handle with
MemHandleFree. There is a real potential for
mischief in this strategy, however. If you fail to free handles
DmNewHandle, they will not be automatically freed when your application quits (unlike in the dynamic heap). Fortunately, at least on a soft reset, ...