Re: svn commit: rev 7961 - trunk/subversion/libsvn_wc

John Szakmeister <john@szakmeister.net> writes:

> Again, whether or not it was allocated in the pool or not isn't the issue
> here. It attempting to reuse a resource that you said you were finished
> with.

You are trying to impose API rules that are not in the present code.
Originally, libsvn_wc was written without access batons or caching and
it's speed was a significant problem. By the time the batons and the
caching were introduced there was a lot of complicated wc code, and
the batons were introduced without attempting to rewrite the code. The
resulting API is more or less accidental.

Try thinking of svn_wc_adm_close as "unlock" rather than as "destroy".
It's the pool lifetime that determines memory validity, the close
function simply removes locks and log files.

-- 
Philip Martin
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org