• 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: -Wall
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: -Wall


  • Subject: Re: -Wall
  • From: Scott Tooker <email@hidden>
  • Date: Wed, 4 Jun 2008 13:34:16 -0700


On Jun 4, 2008, at 1:20 PM, Stuart Malin wrote:

I have decided to write my application "cleanly" -- that is, to not have any compiler warnings. To this end, I have set the "other C Flags" in my Build Settings to -Wall.

Is this the right place to do this? What then is the effect on the Warnings settings of the Build (ignored? do I need to set these checkboxes as well for the various warnings?) Should I be setting - Wall as an "Other Warning Flags" of the Warnings Build Settings, or am I doing this properly by setting as a compiler flag?

It's more a style thing, but I'd set it in Other Warning Flags since it is a flag to activate a set of warnings.


Scott



I am relatively new to Xcode and Cocoa, so pardon me if this question is simple or obvious... (I have attempted to research the answer in advance of posting)

_______________________________________________
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

_______________________________________________ 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
References: 
 >-Wall (From: Stuart Malin <email@hidden>)

  • Prev by Date: -Wall
  • Next by Date: Subversion Hosting
  • Previous by thread: -Wall
  • Next by thread: Re: -Wall
  • Index(es):
    • Date
    • Thread