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

Re: [Issue 1291] Changed - Incorrect path in "not a working copy" error message.

From: <kfogel_at_collab.net>
Date: 2003-05-08 06:42:24 CEST

Branko Čibej <brane@xbc.nu> writes:
> >But to be reeeeeeally honest, I'd rather have the output be
> >OS-independent so that wrapper scripts are instantaneously (more)
> >portable.
> >
> Really? Which wrapper scripts?
> * Shell scripts: inherently non-portable, not worth the bother.
> * Python, Perl: Can handle both forward and backward slashes on Windows.
> * Emacs: ditto.
> * vi: don't know and don't give a damn.


I mean, sure, if you carefully write the script to accept both kinds
of separator. I think Mike means something like: if our output always
uses "/", then anyone who writes an output-parsing script can depend
on "/" as the separator.

I'm not arguing for or against Mike's point, merely trying to make
sure it gets understood. It's meaningless to say that Python and Perl
"Can handle both forward and backward slashes on Windows". They can
handle them if you wrote the script that way, but any such script will
be a bit more complex than a script which just handles one or the

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu May 8 07:24:13 2003

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.