[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: Karl Fogel <kfogel_at_red-bean.com>
Date: Thu, 28 Aug 2008 12:14:53 -0400

Greg Hudson <ghudson_at_MIT.EDU> writes:
> On Thu, 2008-08-28 at 10:48 -0500, Hyrum K. Wright wrote:
>> Reimplementing everything in terms of the latest function introduces a subtle
>> kind of code duplication that I'd rather avoid. And where there's code
>> duplication, there's bugs.
> It might be good to look at some examples.
> My gut reaction is that if it's more concise to use the
> next-most-deprecated API instead of the current API, we didn't
> necessarily improve the API with our changes. But that's just theory.

I tried to do this in the past with some big change, I can't remember
which. I stopped when people objected, but my memory was that it was
mostly drudge-work -- not challenging, just some extra work.

But that was one set of interfaces. I'm not sure it answers the
question of whether wrapping current-API-always would be bug-prone in


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 18:15:08 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.