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

Re: Hide experimental APIs to unblock 1.11 release

From: Julian Foad <julianfoad_at_apache.org>
Date: Fri, 21 Sep 2018 11:29:45 +0100

One important thing I didn't make clear: I propose these APIs go in "public" headers like svn_client.h, not in the "private" header files that are by default omitted from installation.

Stefan, does this make a difference to you? Do you still need to change TSVN build scripts at all for that case? And how will the warnings work out for you in that case? I'd really like to hear how this affects you so we can come to a satisfactory solution.

Julian Foad wrote:
> Julian Foad wrote:
> > Stefan Kueng wrote:
> > > but then that would mean I wouldn't get any compiler
> > > error if I actually use a private and not just an experimental API.
> >
> > That's part of the point -- [...]
> > there's no real practical difference between "private" and
> > "experimental". See my notes on that topic here:
> > https://cwiki.apache.org/confluence/display/SVN/Experimental+APIs
> Re. wanting warnings when using private/experimental APIs: then we
> should arrange for warnings on all such functions. I think it makes a
> lot of sense to do so. Let's look for a good way to do that.

- Julian
Received on 2018-09-21 12:29:54 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.