• 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
Treating some compiler warnings as errors, but not others?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Treating some compiler warnings as errors, but not others?


  • Subject: Treating some compiler warnings as errors, but not others?
  • From: Jens Alfke <email@hidden>
  • Date: Sun, 31 Jul 2011 11:12:07 -0700

Is there a way to tell the compiler to treat warnings as errors, except for certain warnings? I.e. still flag them, just not as errors?

I always build with -Werror because Objective-C reports so many serious issues as mere warnings (i.e. unknown selectors, or messages not understood by the receiver’s declared class). But with the new errors-while-you-type feature, there are some warnings I’d like to just be notified of without getting a red flag and compilation failure — for example, unused variables.

—Jens

Attachment: smime.p7s
Description: S/MIME cryptographic signature

 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

  • Follow-Ups:
    • Re: Treating some compiler warnings as errors, but not others?
      • From: Mimika Oh <email@hidden>
  • Prev by Date: Re: Xcode keeps altering my project.pbxproj files
  • Next by Date: Re: Xcode keeps altering my project.pbxproj files
  • Previous by thread: Xcode 4.1 crashing after radial buttons are inserted into IB project...
  • Next by thread: Re: Treating some compiler warnings as errors, but not others?
  • Index(es):
    • Date
    • Thread