On Sat, Jan 10, 2009 at 12:56 AM, Andrew Farmer <andf...@gmail.com> wrote: > Not to mention, there is no guarantee that future versions of the compiler > will behave identically when processing code that generates warnings. It is > not uncommon for warnings to later turn into errors, or (worse!) incorrect > behavior, especially when optimizations are involved.
Just to pick a nit, this depends greatly on what the warning is about. A lot of warnings are actually about code whose behavior is fully specified by the standard but which is still considered to be iffy. For example, writing if(a = b) will generate a warning under -Wall but its behavior is fully specified and cannot change in any conforming compiler. However it's still a good idea to fix them, and many warnings *are* about code whose behavior could change. Mike _______________________________________________ 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
