Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Date:	Sun, 5 Jan 2003 20:56:40 -0500
From:	Christopher Faylor <cgf AT redhat DOT com>
To:	perl5-porters AT perl DOT org, cygwin AT cygwin DOT com
Subject:	Re: Repost, different list...File::Spec, cygwin, Syntactic vs. Semantic path analysis
Message-ID:	<20030106015640.GA20019@redhat.com>
Reply-To:	perl5-porters AT perl DOT org, cygwin AT cygwin DOT com
Mail-Followup-To:	perl5-porters AT perl DOT org, cygwin AT cygwin DOT com
References:	<012901c2b496$3f4955e0$1403a8c0 AT sc DOT tlinx DOT org> <200301051902 DOT h05J22p26110 AT smtp3 DOT ActiveState DOT com>
Mime-Version:	1.0
In-Reply-To:	<200301051902.h05J22p26110@smtp3.ActiveState.com>
User-Agent:	Mutt/1.5.1i

On Sun, Jan 05, 2003 at 11:02:02AM -0800, Gurusamy Sarathy wrote:
>As far as the Win32 native port goes (I'm not really that cygwin-savvy to
>comment on what should happen for that port) I like to see:

I'm cygwin savvy and pretty perl savvy (although it's been quite some
time since I've posted anything to perl5-porters) but I have to say the
issue of how to deal with win32 paths is pretty uninteresting to me as
far as cygwin is concerned.

I think that if someone wants to use win32 paths they shouldn't be using
cygwin.  One of the primary focuses of cygwin was to isolate the user
from the backslash and colon nonsense.  It's a shame that we don't allow
the creation of filenamess with colons and backslashes but going out of
the way to arbitrarily deal with c: just seems anti-cygwin to me.  And,
attempting to treat /cygdrive/c as special in some way and indicative of
a "volume" also is wrong.  If applicable, /cygdrive/c should be
considered a mount point and /cygdrive should be considered to be
equivalent to a "devfs" system on linux.

I sympathize with the headaches involved with trying to accomodate win32
paths and will obviously support whatever decisions are made in this
regard but I would like to suggest that, for the most part, Cygwin path
handling should be as close to UNIX as possible.  Cygwin short circuits
most of its special handling when it sees a ':' or a '\'.  There is no
mount table interpolation in such a case.  To be consistent, I think it
makes sense for any perl cygwin module to automatically punt to win32
path spec handling when it sees those with the possible caveat that "a:"
== "a:\" on cygwin.

To address another issue in this thread, we won't be modifying cygwin to
allow the use of /cygdrive/c to mean "the current directory on drive c".
That's only an "OS" feature on Windows 9x and it clearly has no place in
a UNIX-like environment.  Even if this was not the case, the fact is
that this is long-established behavior for cygwin.  Changing it now
would not be a good idea without a really really good reason.

cgf
(cygwin project lead)
--
Please use the resources at cygwin.com rather than sending personal email.
Special for spam email harvesters: send email to aaaspam AT sources DOT redhat DOT com
and be permanently blocked from mailing lists at sources.redhat.com

--
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/

- Raw text -