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

Re: Deferring the removal of temp APIs

From: Hyrum K Wright <hyrum_at_hyrumwright.org>
Date: Fri, 10 Jun 2011 10:38:30 -0500

On Fri, Jun 10, 2011 at 10:33 AM, C. Michael Pilato <cmpilato_at_collab.net> wrote:
> On 06/10/2011 07:39 AM, Daniel Shahaf wrote:
>> Julian Foad wrote on Fri, Jun 10, 2011 at 11:17:11 +0100:
>>> The consensus seemed to be [1] that we can add/remove/change private
>>> APIs during the 1.7.x series,
>> Indeed that's the consensus I have sensed.  I am not sure if we include
>> the svn* clients in this "upgrade en bloc" group, but Philip's recent
>> work on "1.6 client, 1.7 libraries" does highlight one reason for
>> wanting to minimize the use of private APIs in the svn* tools.
> I would be in favor of a policy that explicitly disallows our binaries from
> using private libraries.  I believe it would serve to force us to think a
> bit more globally in terms of what would be useful to expose for the benefit
> of other clients.

Certainly, but some class of APIs deserves to be private, in my
opinion. Our SQLite wrappers, for instance, are used throughout
Subversion, but have no business being exposed outside of it. Nobody
needs to use them, and exposing them would cause an unneeded
maintenance burden in the future.

Received on 2011-06-10 17:39:04 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.