Hello James,

"James Dennett" <[EMAIL PROTECTED]> schreef in bericht
> J.Bijsterbosch wrote:
[ snip ]
> >>and didn't remember Windows uses path names which need special
> >>treatment.
> >
> > Hmm, what you call special treatment<g> comes from pythons deep
underlying C
> > and C++ language heietidge I presume. A backslash in a C or C++ string
> > the following character is a so called escape character, like \n
> > a newline and \r a return to the beginning of a line.
> > If you really want a backslash you need to type it twice like so \\. Has
> > nothing to do with Windows...;-))
> Actually, it does have a connection to Windows.
> On Unix, backslashes are rarely used for anything *except* escape
> characters.  Pathnames tend not to include backslashes, so in most
> cases it's not necessary to escape backslashes in path names.

I know<g>, I've had mandrake installed for some time until that pc died on
me, the pc that is, not mandrake...

> On Windows, however, backslash is a valid path separator, and must be
> escaped.
> So, on Unix, for a path separator, you type "/".  On Windows you
> can either do the same, or type "\\".  (Or (ab)use raw strings.)

Okay, point taken, but I still think it's more a C(++) string thing than a
issue. I could of course argue that the backslash path separator is there
for backward
compatebility with Dos, but I won't, much to off topic...;-))

>  James

Greetings from overcast Amsterdam,



Reply via email to