[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: An unexpected effect of new 'deprecated' tags.

From: Julian Foad <julianfoad_at_btopenworld.com>
Date: Thu, 28 Aug 2008 10:28:46 +0100

On Thu, 2008-08-28 at 09:27 +0100, David O'Shea wrote:
> On 28/08/2008 04:44, Karl Fogel wrote:
> > Now, what do we do to avoid being spammed with compilation warnings
> > for the rest of our lives? Just always reimplement everything in
> > terms of the newest function? Ick. Or is there some way to mark
> > calls as known-and-okay, so they won't cause a compilation warning?
> You can use the "-Wno-deprecated-declarations" option in GCC to suppress
> these warnings. I'm not sure about other compilers though...

That's fine as an all-or-none approach, and we might want to turn them
off by default, but what we really want is for the warnings to be
suppressed inside deprecated functions.

According to GCC's docs, where __attribute__((deprecated)) appears on a
data TYPE definition, GCC SUPPRESSES the warning where a deprecated type
is used inside another deprecated type definition.

I have no idea why GCC doesn't behave the same way w.r.t. functions.

Perhaps another version of the compiler will do what we want. Perhaps
the Microsoft compiler does behave that way.

In the meantime, I don't know of a better solution than just choosing
whether to see all of them or none of them.

- Julian

To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-08-28 11:29:09 CEST

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.