Re: Per-file Warnings suppression?
Re: Per-file Warnings suppression?
- Subject: Re: Per-file Warnings suppression?
- From: Dave Carrigan <email@hidden>
- Date: Wed, 1 Oct 2008 19:40:00 -0700
On Oct 1, 2008, at 7:27 PM, Brian Stern wrote:
While the per file compiler flags is a powerful feature of Xcode it
is somewhat obscure. Imagine that you inherit a project from
someone else that has 1000 source files and some number of per file
compiler flags to turn off warnings or modify optimization or really
anything. How would you sort that out or track down bugs that would
have been revealed by having warnings turned on?
In addition, I like having warnings, so I would like to turn them off
with a pragma before including some vendor's crappy warning-generating
header, then turn them back on afterwards. Per-file flags won't even
work for that use case.
Unfortunately, the way the GCC ones seem implemented now, that will
never be possible. Specifically, I'm talking about the text that says
it is not reliable except at the very top of the file.
Microsoft really did get that one right with pragma warning push/
disable/pop, and it would be nice if gcc could do the same. But in
reality, that's a complaint for the gcc list, not the xcode list.
--
Dave Carrigan
email@hidden
Seattle, WA, USA
Attachment:
PGP.sig
Description: This is a digitally signed message part
_______________________________________________
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