When did Windows start accepting forward slash as a path separator?

David Schnepper davidsch at verity.com
Sat Sep 27 00:31:06 CEST 2003


I use cygpath --mixed mode for converting.
http://cygwin.com/cygwin-ug-net/using-utils.html#CYGPATH

>From experimenting, a backslash seems required only at
the beginning of a path, eg:

cd /orant          Error

All the following are OK

cd \orant          
cd c:/orant
cd orant/win
cd \orant/win

Dave Schnepper

-----Original Message-----
From: python-list-admin at python.org
[mailto:python-list-admin at python.org]On Behalf Of Stephen Ferg
Sent: Thursday, September 25, 2003 4:51 PM
To: python-list at python.org
Subject: When did Windows start accepting forward slash as a path
separator?


I have a question that is not directly Python-related.  But I thought
I'd ask the most erudite group that I know... :-)

When did Windows start accepting the forward slash as a path separator
character?

At one time, it was accepted as a truism that Windows (like MS-DOS)
was different from Unix because Windows used the backslash as the path
separator character, whereas Unix used the forward slash.

But now, among a small group of cognoscenti, it is a truism that this
is a myth, and that Windows will allow you to use either the forward
or the backward slash as a pathname separator.

I hypothesize that originally Windows accepted only the backslash, and
then at some time it changed to accept the forward slash as well. 
Does anyone know when that change occurred?  Was it with the
introduction of support for long filenames in NT and Win95?
-- 
http://mail.python.org/mailman/listinfo/python-list






More information about the Python-list mailing list