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

Re: [RFC] Mark deprecated functions with SVN_DEPRECATED / __attribute__((deprecated))

From: Julian Foad <julianfoad_at_btopenworld.com>
Date: Tue, 19 Aug 2008 13:10:19 +0100

On Tue, 2008-08-19 at 13:14 +0200, Arfrever Frehtes Taifersar Arahesis
> 2008-08-18 23:25:34 Greg Stein napisał(a):
> > Well, by definition, we don't need the developer to upgrade their
> > software. They should be able to freely use the old API with no
> > consequences. Thus, there is no rational reason for us to spam them.
> Such messages shouldn't be treated as spam. They would be seen mostly only
> by developers of software which uses Subversion libraries. People who don't
> like warnings can use the '-w' compiler option.

No. Greg is right. If a developer upgrades their version of Subversion,
and then sees lots of new warnings that they can't turn off
independently of other warnings, that would be spam.

> > And yes, we can keep docstrings in the deprecated header so that
> > people can figure out how to upgrade their calls.
> Please don't move declarations of all deprecated functions to one header.
> IMHO it would only create a disorder.

Yes, +1. I hope greg meant to create a set of deprecated headers, one
corresponding to each normal header. Something like:

#include svn_wc_deprecated.h

- 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-19 14:10:42 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.