"Stringer" <[EMAIL PROTECTED]> wrote
>
> Note: Some people suggest writing a custom new() to avoid the
> heap allocation issue, but personally I don't like creating my
> own version of a standard function.
>
OK, I'm curious. How does a custom new() overcome the heap issues. Do you
mean that they're creating the object in a locked chunk? If so, wouldn't
you have to leave that chunk locked for the life of the program (or, at
least, for the life of the object). Maybe that's the key - use this
technique for short-lived objects.
More importantly, since you can't write directly to that area of memory do
you have to use DmWrite for all property manipulation?
Chris Tutty
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
