Public wc_db functions?

Greg,
As you can tell, I've started punching some of the wc_db API changes
through to the public API. I'm wondering how we are going to handle
entires, though. For instance, several places in libsvn_client, we
grab an entry, and then use various fields from it. Internal to
libsvn_wc, we'd replace that with a call to read_info(), but I do not
want to expose that interface beyond libsvn_wc. Any suggestions on
how to push this through to libsvn_client?

[I've thought about introducing specific APIs (svn_wc_entry_url(),
svn_wc_entry_kind(), etc.), but it seems that that way lies madness,
as we get into an API proliferation trend that appears hard to stop.]

-Hyrum

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=2358907
Received on 2009-06-02 23:01:26 CEST