[EMAIL PROTECTED] wrote:
The project runs successfully at the beginning on clie,but being approximately a half,the error occures. if there is a NULL pointer on the clie,why there is not on zodiac? if the clie handles NULL pointer is different from zodiac,why it is successful at the beginning?
The correct answer to this question is this: if you have an error in your application where you are accessing a pointer which is invalid, the implementation (the compiler and the device that runs the compiled code) is free to do anything it wants. The behavior is undefined. Therefore, you should EXPECT inconsistent results until you resolve the problem. If you access a invalid pointer, then crashing is a perfectly reasonable behavior for the system. Also, working perfectly is a perfectly reasonable behavior for the system. However, if the system does work as you expect, you should not see that as an indication that nothing is wrong and that your code is written correctly but only incompatible with other systems. One possible answer, by the way, is that you are doing a MemPtrNew() and the Zodiac (which has a large heap) returns a valid pointer but the Clie (which might have a smaller dynamic heap) would return NULL for that MemPtrNew(). But that is only one possible explanation and there are many others. The best plan is to see what parts of your code this problem is related to, and then check over the code for coding errors. - Logan -- For information on using the PalmSource Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
