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

Re: Private header files [was Re: svn commit: r33207 - branches/file-externals/subversion/libsvn_client]

From: Blair Zajac <blair_at_orcaware.com>
Date: Sat, 20 Sep 2008 10:40:52 -0700

Greg Stein wrote:
> Hmm. I saw it more as private subsystems, or sharing data between client
> and server bits.
> The readme is kinda hard to argue with... Hmm. I'll take a look. It just
> seems that if a library needs functionality from another, then we should
> tweak the public api cuz somebody else may need it.

Yeah, there's nothing stopping us from promoting a function from private to public.

It seems better to put a function in private unless you know you'll need it in
the public API. We do enough versioning of functions as it is, better to let an
API develop in private with our own internal usage and promote it to public when
needed then have a potentially unbaked call sit in public that we need to
maintain the ABI.


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-20 19:41:09 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.