Re: Make "incompatible pointer type" an error, not a warning
Re: Make "incompatible pointer type" an error, not a warning
- Subject: Re: Make "incompatible pointer type" an error, not a warning
- From: Chris Espinosa <email@hidden>
- Date: Mon, 9 Feb 2009 10:19:17 -0800
On Feb 9, 2009, at 10:10 AM, Sean McBride wrote:
On 2/9/09 9:20 AM, Scott Johnson said:
I get a warning in Xcode 3.0 in my C Carbon app which is "warning:
initialization from incompatible pointer type". This warning can be
dealt
properly by casting the pointer. This is all great, but I would
actually
prefer this warning be an error, so that I am required to cast the
pointer
assignment, and I do not want to open up a whole series of other
warnings
and errors in the process.
Just google "gcc warning to error". First hit: the gcc docs! :)
-Werror=
Make the specified warning into an error. The specifier for a
warning is
appended, for example -Werror=switch turns the warnings controlled
by -
Wswitch into errors. [...]
That's half his answer. The other half is "what flag controls
incompatible pointer type conversions?"
The answer is -Wpedantic, and there's a special switch specifically to
turn pedantic warnings into errors: -Wpedantic-errors. Unfortunately
it doesn't satisfy the OP's requirement of not turning other warnings
into errors; it will flag all the pedantic warnings, which are
numerous and, well, pedantic.
Chris
_______________________________________________
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