Dave, > You're wrong on this part. MemPtrNew allocates a non-movable chunk that > is immune to compaction or defragmentation. MemHandleNew allocates a > movable chunk that will be essentially flagged as non-movable when you > lock it with MemHandleLock.
Yikes!! :-P Thanks Dave for that piece of info. Apologies for the misinformation guys. Dave, would you please take this opportunity and let us know furhter in this direction ? I have read somewhere that palm devices dont have any MMU. Let me keep it in this way please...My understadning is that Palm OS does not have any virtual memory...so its all segment/chunk oriented stuff. Does that the reason why any resource in Palm cannt be larger than 64K ? And then....cannt I hide the physical addresses behind the handles ? I thought a handle is really a pointer to pointer. I particularly wanna know more on how does the system make up for lack of a typical MMU ? > It's perfectly safe to allocate long-lived pointers with new. The only > thing is that it can cause memory fragmentation (this is generally true > in any OS, but on small-memory systems it can be more of a > problem). However, the same thing can be said if you allocate a handle > and lock it for the length of the program. Neat. So till date I was under wrong impression. Bleeh!! Thanks again Dave for that beautiful piece of info. -Viren -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
