Ben Combee wrote:
The m125 will have a smaller stack, so deeply nested code that uses a lot of stack space might not run on it, but it would run on the Tungsten E. The T|E also has a bit more dynamic heap for MemPtrNew allocations.
Hmm, I thought the size of the stack was simply determined by the 'pref' resource in the app's PRC, so that it should be the same on any model as long as the system is able to successfully launch the app. Or is it more complicated than that? - Logan -- For information on using the PalmSource Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
