I am about to release a first public beta of my application. So far, I did all my testing with CW 8.3 optimizations off. Can I now blindly (...) turn optimizations on, check auto (smart) inlining and be confident things will work the same, albeit faster (hopefully)?
The program should work the same, but there can be differences. Mainly, code that does bad stuff may do different bad stuff when optimized. Overwriting a buffer might modify a different set of variables in optimized code, for example.
Correct me if I'm wrong, but I could not find a centralized documentation on the CW C/C++ Language Settings dialog. I'm especially wondering about deferred inlining and the effect of the inlining drop-down list if the Auto inlining is not checked.
Auto-inlining tells the compiler to try inlining any function, even those not declared with "inline". With this off, the compiler will only attempt to inline functions that are explicitly marked as inline.
Lastly, how can I strip the debug symbols to ship a smaller PRC?
Turn off the "macsbug symbols" setting in the 68K processor panel. Most of the debug info is in the .psym file, so it doesn't affect your PRC file size.
--
Ben Combee <[EMAIL PROTECTED]>
CodeWarrior for Palm OS technical lead
Palm OS programming help @ www.palmoswerks.com
-- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
