Path: utzoo!attcan!uunet!cs.utexas.edu!usc!elroy.jpl.nasa.gov!forsight!jato!mars!kaleb
From: kaleb@mars.jpl.nasa.gov (Kaleb Keithley)
Newsgroups: comp.sys.ibm.pc
Subject: Path name separators, was Re: Need input for future DOS release
Keywords: future DOS release
Message-ID: <3204@jato.Jpl.Nasa.Gov>
Date: 27 Mar 90 18:20:25 GMT
References: <53686@microsoft.UUCP>
Sender: news@jato.Jpl.Nasa.Gov
Reply-To: kaleb@mars.UUCP (Kaleb Keithley)
Organization: Jet Propulsion Laboratory, Pasadena, CA.
Lines: 17

In article cs4g6ag@maccs.dcss.mcmaster.ca (Stephen M. Dunn) writes:
>In article <246@edpmgt.UUCP> gpitcher@edpmgt.UUCP (Glenn Pitcher) writes:
>$Couldn't the shell be altered to intercept those directory requests and   
>$remap the characters before the actual open (or whatever) command is issued?
>
>   If you alter the shell, this would only affect commands issued from the
>shell.  Pathnames entered within applications would still require the use
>of the \ regardless of what you set.

Wrong, wrong, wrong.  Unless the application has *stupid* filename validation,
'/' and '\' are equivalent to DOS.  RTFM.  It's only COMMAND.COM that insists
on checking for `\` as a path separator.

kaleb@mars.jpl.nasa.gov            Jet Propeller Labs
Kaleb Keithley

spelling and grammar flames > /dev/null