On 30.09.2018 20:51, Stefan Küng wrote: > > > On Thu, Sep 20, 2018 at 10:13 PM Julian Foad <julianf...@apache.org > <mailto:julianf...@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 > 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. > > > How about moving the experimental headers into a separate subfolder? > Right now, there's: > subversion/include > subversion/include/private > 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 Subversion libraries. -- Brane
