Turn 'em off. What are you gaining by having them on? A 1000 bytes? My 255K program goes down to 246K from 0 to 4 in optimizing for size, but now I have a program that might not work anymore in some places (in my experience), and certainly one I can't easily debug anymore.
My program has almost no need for speed, so I've never even tried to optimize for speed. At least back it off until it generates code that works (assuming there isn't actually a bug there in your code, even with optimizations off). IMHO. YMMV. Kevin -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Luc Le Blanc Sent: Friday, December 05, 2003 9:12 AM To: Palm Developer Forum Subject: Debugging "despite" CW 8.3 optimizations When I compile my program with full CW 8.3 optimizations, it crashes when trying to lock a DB record it obtained with a wrong index. This does not occur without optimizations. I tried tracking the problem with the debugger, but nothing makes sense: variables reported in the monitor window barely resemble what they should be, even after going over a line such as index = 0. The CW settings dialogs warns that debugging with optimizations on is going to be harder. What is the best strategy, then? -- Luc Le Blanc -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/ ------------------------------------------ The information in this transmittal and any attachments are confidential and intended only for the recipient(s) listed above. You are hereby notified that any unauthorized distribution or copying of this transmittal or its attachments is prohibited. If you have received this transmittal in error, please notify invivodata immediately at (831) 438-9550. ------------------------------------------ -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
