On Thu, Sep 20, 2018 at 10:13 PM Julian Foad <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. I suggest to add subversion/include/experimental and put the experimental headers there. this would have the advantage that those who want to use the experimental features won't have to add the private folder to the compilers include path. Stefan
