Hi all.
I'm new to programming on Palm OS, and I have a few questions about the "dreaded" 64K limit (it inspires dread to me anyway!).
First, my target is the Tapwave Zodiac. For the moment I have no other Palm device targeted. I'm using Codewarrior 9.2 on Windows.
I'm also writing my code to target native ARM only, as provided by CW 9.2. I don't plan to include my application (game) files in resources, if possible.
- Since it runs on the latest 5.x version of Palm OS, is the 64K limit still there, and do we need to take special precautions?
Yes, it's there, but there are workarounds. The Tapwave Zodiac doesn't have the 64K limits on resource size over HotSync that other devices have, but the other OS limits are still there.
- Does MemPtrNew() solves the 64K limit? Can I just use it instead of malloc and access the memory in a linear fashion?
MemPtrNew doesn't, but MemGluePtrNew (from 68K code) will allocate >64K memory.
- Are new & delete operators available? I've read in some devnotes of CW 9 dated Sept 2002 that they are not.
See my articles on palmoswerks.com -- new/delete aren't implemented in the PNO ARM runtime, but they are there in the Tapwave Native Application runtime, and you can define inline versions of them that call your own operators.
If you're going to be writing ARM code for the Zodiac, you'd be better served in the pno-forum group.
-- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
