On 21.04.2011 17:00, Julian Foad wrote:
This is a post-1.7 RFC.
Most libsvn_client APIs allow the caller to throw either URLs or working
copy paths at the API and then it just does the right thing. But does
this paradigm make sense for APIs such as this one?
svn_client_propset4() operates on either WC paths or URLs. Although its
purpose is the same either way in general terms, the differences are
substantial, and in particular the parameters needed by the API are
substantially disjoint. The differences are highlighted by its doc
string which looks like this in outline:
I'm all for it. In TSVN I separated the two situations (urls and paths)
into two separate classes already since it's just easier to deal with it
that way.
Stefan
--
___
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.net
