Re: Hide experimental APIs to unblock 1.11 release
On 30.09.2018 20:51, Stefan Küng wrote:
> On Thu, Sep 20, 2018 at 10:13 PM Julian Foad <julianfoad_at_apache.org
> <mailto:julianfoad_at_apache.org>> 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
> > 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.
> How about moving the experimental headers into a separate subfolder?
> Right now, there's:
> and the experimental headers are now in subversion/include/private.
No they are not. The shelving functions, for example, are declared in
subversion/include/svn_client.h. Private functions are in
subversion/include/private, but those are should not be used outside the
Received on 2018-10-01 00:56:06 CEST
This is an archived mail posted to the Subversion Dev