Re: Use existing __ namespace in public headers for experimental APIs to unblock 1.11 release

Julian Foad wrote:
> > 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.

There's a nomination in the STATUS file for this change, now.

Can anyone please review or otherwise comment on it?

> [...] The key thing was we needed to move them
> out of the strong compatibility rules, and using the existing "__"
> namespace is sufficient for that.
>
> > 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