Re: Silencing deprecated warnings in deprecated functions

We control the warnings, so the deprecated.c file could just define
SVN_DISABLE_DEPRECATED before including any headers.

Also note you can use deprecated.c everywhere; they're in separate
dirs, so no problem.

Cheers,
-g

On Sep 6, 2008, at 22:27, Blair Zajac <blair_at_orcaware.com> wrote:

> I don't like to see warnings when I compile svn. So is there a way
> we can silence the deprecated warnings when functionN() calls
> functionN+1() which is also deprecated to functionN+2().
>
> Can we do that by marking functionN+1() somehow that its ok to call
> it?
>
> If not, then we could move all the deprecated functions into new
> deprecated.c files for each library and use -Wno-deprecated-
> declarations only on that one. Say client_deprecated.c for
> libsvn_client/ functions.
>
> Blair
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
> For additional commands, e-mail: dev-help_at_subversion.tigris.org
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-09-07 12:17:14 CEST