This is the mail archive of the
cygwin@cygwin.com
mailing list for the Cygwin project.
RE: Repost, different list...File::Spec, Cygwin, Syntactic vs. Semantic path analysis
- From: Elfyn McBratney <elfyn-cygwin at sickpuppy dot co dot uk>
- To: "LA Walsh" <law at tlinx dot org>, cygwin at cygwin dot com
- Date: Mon, 6 Jan 2003 00:30:07 -0800 (PST)
- Subject: RE: Repost, different list...File::Spec, Cygwin, Syntactic vs. Semantic path analysis
- Reply-to: cygwin at cygwin dot com
> If a user calls the 'normalize' function, it should convert it
>to "\" -- since that is the OS standard/default -- HOWEVER...
I tend to agree that as windows uses the back-slash as a default path
seperator so should `normalize' but also in the interest of
compatability with windows 95 (in dos mode) as it doesn't support the
forward-slash path seperator.
> In "cmd.exe", you can type 'dir \' or you can type 'dir "/"'.
>You have to quote the "/" so it won't be interpreted as a switch
>character -- but the underlying OS seems to not really care which you
>use and neither should Win32.
A bit OT but dir does not support the forward slash pathsep even when quoted:
C:\WINNT>dir "/"
Directory of \\
File Not Found
Although the win32 api supports both one takes more work as paths containing forward-slashes are converted to back-slashes*. I know this is being petty but if different style paths cause problems surely it would make sense to follow the standard the OS follows?
Elfyn
elfyn@exposure.org.uk
_____________________________________________________________
www.smokeJet.com - Free UK Internet Services
_____________________________________________________________
Select your own custom email address for FREE! Get you@yourchoice.com w/No Ads, 6MB, POP & more! http://www.everyone.net/selectmail?campaign=tag
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/