On Mar 4, 2009, at 5:03 PM, Nick Zitzmann wrote:
Yes; I pointed that out to you yesterday. You can, if you wish, turn on the warnings/errors option for your target in Xcode to treat all warnings as errors. You should also set a global breakpoint on objc_exception_throw so you can catch exceptions like that one.
Yeah, that was an odd situation... one of those things right in front of my face that I ignored and missed (run log)... since it didn't work, I just commented it out and went on with other things and waiting for responses on the list... so, I didn't notice the either compiler warning or xcode run log message - until I happened on the spelling error myself (THOUGH, I sure wish I had seen your message first -- stupid delayed Mail delivery!).
Breakpoint is a good idea - I usually do that for C++. As for warnings are errors - not possible, because I'm working with a larger beast that has plenty of benign but odd warnings that I'm not authorized to spend the time removing. Sigh.
Thanks again, for all the good advice from everyone. M -- Mark D. Gerl, Multimedia Design Group, <mailto:mg...@mmdesigngrp.com> _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
