Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Subject: RE: Repost, different list...File::Spec, Cygwin, Syntactic vs. Semantic path analysis From: Robert Collins To: cygwin@cygwin.com Cc: LA Walsh In-Reply-To: <20030106083008.4C1334385@sitemail.everyone.net> References: <20030106083008.4C1334385@sitemail.everyone.net> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-Wskmz4RO/LFowj9R3kiq" Organization: Message-Id: <1041842190.31517.16.camel@lifelesslap> Mime-Version: 1.0 Date: 06 Jan 2003 19:36:30 +1100 --=-Wskmz4RO/LFowj9R3kiq Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Mon, 2003-01-06 at 19:30, Elfyn McBratney wrote: > 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? Right, so: Perl for Cygwin uses "/" Perl for win32 uses "\" and ":". Seems pretty straight forward to me. Cygwin may be 'just a partial posix layer', but if you are compiling for it, you should use "/" delimited paths. Rob --=20 GPG key available at: . --=-Wskmz4RO/LFowj9R3kiq Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQA+GUAOI5+kQ8LJcoIRAsRjAJ0WS7/MUVZGMCeQwQczrC3RIcJrKwCdHXHP pCDI/u7iwjGAf4FN+mgq3LI= =fDWE -----END PGP SIGNATURE----- --=-Wskmz4RO/LFowj9R3kiq--