Greg Stein wrote:
> I believe it is because the design of that API assumes it is a
> "forgivable problem". The caller is *trying* to acquire an access
> baton, but if it can't get one, then the caller can decide what to do
> with that information.
I see. Though it's still strange.
>
> Not a problem. I'll just warn you, though, that the access baton code
> is *going away*. It is overly-complicated and under-specified. There
> are some pretty crazy subtleties in how access batons are used and
> managed.
To be honest, I'm still hazy on the topic of batons.
>
> Instead, the svn_wc.h code is going to switch to something closer to
> libsvn_wc/wc_db.h. The latter is a private header, but its concepts
> and patterns are very close to what I'd like to see in a revamped
> svn_wc.h.
What's the ETA on the move on svn_wc.h? I'll read up on
wc_db.h as well.
>
>> ...
>> PS: While I'm on the topic of svn_wc.h, if I find a
>> docstring 'error', who do I report it to? Thanks
>
> This mailing list. There are no "owners" of that header, other than
> the developers on this list, as a whole.
>
I'll definitely keep that in mind.
Thanks, Greg.
Edmund
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=1748419
Received on 2009-04-16 16:46:58 CEST