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

Re: Too many warnings

From: Mark Phippard <markphip_at_gmail.com>
Date: Wed, 4 Nov 2009 12:08:56 -0500

On Wed, Nov 4, 2009 at 12:05 PM, Philip Martin
<philip.martin_at_wandisco.com> wrote:
> Mark Phippard <markphip_at_gmail.com> writes:
>> On Mon, Nov 2, 2009 at 9:18 AM, Branko Cibej <brane_at_xbc.nu> wrote:
>>> Bright ideas welcomd; I'd be happy to help with ridding our code code of
>>> the deprecation warnings.
>> Didn't we do this to ourselves in on purpose?  I recall it was fairly
>> recently that someone decided to mark all of our older public API as
>> deprecated so that you would get these warnings.
> I configure with 'CFLAGS=-DSVN_DEPRECATED=' to remove them.  Do we
> really want these warning to be enabled by default for third parties?
> Our API guidelines mean that the deprecated functions will continue to
> work at least as well as in the past.  Adding warnings to other
> projects' builds is not very friendly.

That was my point ... that we could undo all of this anytime we want.

I am not certain that all of the needless churn it has caused to make
all code use the newer API has been all that beneficial either.

As a communication mechanism to let someone know there is a newer API
it seems sort of useful.

BTW, congrats on the new job and welcome back!

Mark Phippard
Received on 2009-11-04 18:09:10 CET

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