DJ,
There is a need for two functions. One to use when supplying input, the
other to take output from svn and convert into native form.
Maybe the output path version is simply a function that replaces each
'/' with '\'? I believe I always know by context if its a URL or path
and can avoid calling on a URL trivially.
Barry
At 15-11-2003 01:26, D.J. Heap wrote:
>Barry Scott wrote:
>>Greg, I think you are right a simpler client API is required. Which
>>is why rapidsvn and pysvn are based on the svncpp interface.
>>I fail to see why you think supporting unix and windows paths is
>>so hard. Python has solved the problem, My Emacs has solved the
>>problem and lots of other portable apps. I hope this some thing
>>that gets fixes after 1.0 is out.
>>Sigh and I just found another assert for input error. Seems I
>>must not have a trailing / on a path.
>>Barry
>
>I believe it's the utf8 conversion that is problematic, not the path style
>differences -- if libraries call each other they can't keep utf8
>converting the path and so would have to deconvert it first, as Greg mentioned.
>
>The function I pointed out earlier handles all the cases you've had
>trouble with so far. I'll put together a patch that makes that code a
>public function tomorrow and see if it's acceptable -- it should be a
>rather small change and would make clients lives easier.
>
>DJ
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun Nov 16 02:05:09 2003