Re: pragma nowarn
Re: pragma nowarn
- Subject: Re: pragma nowarn
- From: Philip Aker <email@hidden>
- Date: Wed, 12 Dec 2007 05:49:49 -0800
On 2007-12-12, at 04:47:30, Alastair Houghton wrote:
I have yet to see a situation where there is genuinely a reason for
not changing the code to fix a warning, assuming that you don't
enable any of the sillier warning flags.
10.4 was a good place to remark deprecated calls and replace them. I
had a warning about GetFNum() throughout 10.4 because OSADisplay()
required an obsolete format and a replacement call was not available
until 10.5. I did not want to have a warning about code that worked
for years since I have 'warnings are errors' turned on. I actually
didn't know that pragma was available and so turned off warnings for
the file in question. Which was not really what I wanted.
Is there something silly about 'warnings are errors' for you? I find
it saves me a lot of grief. For instance purging FSSpecs in 10.4 at
my leisure was one of the things that made this code hunk transition
to Leopard an easy task.
Philip Aker
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