Yeah, I'm wondering if that's a problem... but according to the Palm OS
Companion, MemPtrFree should do the same thing as using MemPtrRecoverHandle
and then using MemHandleFree:
"When you no longer need the chunk, call MemPtrFree, which releases the
chunk even if it�s locked."
Am I out to lunch locking the handle when I create a string, and unlocking
it when the string is destroyed? Would it be a lot better to unlock the
handle after using MemHandleNew, then lock it down whenever I need access to
the Ptr?
Thanks,
-Mark
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Armel
Asselin
Sent: Thursday, June 05, 2003 8:41 AM
To: Palm Developer Forum
Subject: RE: Memory problem and Zire debugging
Hello,
I did not dig into your problem much but I find it strange that you do
MemHandleNew
MemHandleLock
...
MemPtrFree
usually either you do:
MemHandleNew
MemHandleLock
...
MemHandleUnlock
MemHandleFree
or
MemPtrNew
...
MemPtrFree
hope it helps
Armel
--
For information on using the Palm Developer Forums, or to unsubscribe,
please see http://www.palmos.com/dev/support/forums/
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/support/forums/
