[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

deprecate all of svn_wc.h ?

From: Greg Stein <gstein_at_gmail.com>
Date: Thu, 8 Apr 2010 17:02:00 -0400

Hey all,

It has come up a few times on IRC discussions: "we should never have
exposed libsvn_wc, just libsvn_client".

Well, we've already exposed it, so we need to at least keep that stuff
around. But moving forward... should new functions continue to be
exposed? Or should all new functions go into svn_wc_private.h?

This question is (probably) directed at our (GUI) client developers.
Do you ever use WC functions? And if you do, then which ones? Where is
svn_client.h insufficient, leading you to use svn_wc.h APIs?

Note: I think the separation is a Good Thing, for our benefit, but we
don't necessarily have to expose the WC layer to downstream

Received on 2010-04-08 23:02:29 CEST

This is an archived mail posted to the Subversion Dev mailing list.