• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag
 

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Showing more warnings possible in Xcode?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Showing more warnings possible in Xcode?


  • Subject: Re: Showing more warnings possible in Xcode?
  • From: Michael Ash <email@hidden>
  • Date: Sat, 30 May 2009 06:30:02 -0400

On Fri, May 29, 2009 at 11:37 PM, Gwynne Raskind
<email@hidden> 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 (email@hidden)

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:

This email sent to email@hidden

References: 
 >Showing more warnings possible in Xcode? (From: Eric Hermanson <email@hidden>)
 >Re: Showing more warnings possible in Xcode? (From: Graham Cox <email@hidden>)
 >Re: Showing more warnings possible in Xcode? (From: Gwynne Raskind <email@hidden>)

  • Prev by Date: Re: Question about NSFileHandle class
  • Next by Date: Re: [ NS KeyedArchiver ] archiveRootObject:toFile: hoses my directory's permissions
  • Previous by thread: Re: Showing more warnings possible in Xcode?
  • Next by thread: Re: Showing more warnings possible in Xcode?
  • Index(es):
    • Date
    • Thread