>I don't know why I need to care about a4 support to be honest. I'm sure >there's a reason, but I've never needed it thus far. Can you elaborate on >the better emulator support? CW7.1 works 95% correctly with the emulator for >me /w only one problem In know of (when an app crashes while debugging, >stack variables are sometimes not available). How did CW8 change?
Could be a result of the Emulator itself evolving in the meantime too, to be honest. With 7.0 it used to hang very often and I had to close both the emulator (often through the task manager) and the IDE and then run them again. Ever since installed CW8 the problem went away. If you don't need the a4 support (that is, the need for globals/virtual tables/exceptions) at any time, or if you can get away with it then you don't need the extended mode. While arranging global memory for your app can be done with regular SDK calls, the support for virtual methods and (less often) exceptions might be very important for many. A good example might be WordSmith, which, I believe uses C++ actively. The use of a4 allows gcc to utilize glibs, which is easier and more optimized code extension modules than shared libs are. Again, there are pros and cons and I am not advocating for either here. Bottom line is, if you design, code and sell well without CW8 then you really don't need it. Especially now when CW9 is in sight. - bobby -- 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/
