On Fri, May 29, 2009 at 11:37 PM, Gwynne Raskind <gwy...@darkrainfall.org> wrote: > In short, you can't get this warning in a Debug-style build unless you want > to sabotage your debugging efforts by adding optimization.
Your best workaround for this is probably to use the Clang static analyzer instead. It's not quite as convenient (needing to run as a separate step instead of being integrated into the build) but it will catch stuff like this and much more besides, and it's more intelligent than gcc about what it finds. 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
