> Speaking as a battle-hardened QA manager, the one simple step of > turning on all warnings and removing them
Absolutely. Which is why pointless warnings really annoy me! FYI, I'm not talking about Xcode/gcc here. I'm thinking of an old version of Watcom, in which a warning was generated for every case of a child class not overriding a descendant's virtual method! (Note: virtual, not pure virtual which of course was an error.) And these days I have ****loads of deprecated warnings that I won't be able to deal with for a while yet, which sometimes obscure useful warning about actual mistakes... Oh well... -- Scott Ribe [EMAIL PROTECTED] http://www.killerbytes.com/ (303) 722-0567 voice _______________________________________________ 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 [EMAIL PROTECTED]
