From:	khan AT xraylith DOT wisc DOT edu (Mumit Khan)
Subject:	"./file" vs ".//file" pathname ambiguity in b16
20 Nov 1996 11:09:06 -0800 :
Sender:	daemon AT cygnus DOT com
Approved:	cygnus DOT gnu-win32 AT cygnus DOT com
Distribution:	cygnus
Message-ID:	<9611201717.AA18643.cygnus.gnu-win32@modi.xraylith.wisc.edu>
Original-To:	gnu-win32 AT cygnus DOT com
Original-Sender:	owner-gnu-win32 AT cygnus DOT com

Should "./test.out" and ".//test.out" resolve to the same path? B16 is
resolving the first one correctly (current directory) and the second one 
to be "/test.out". Is this expected? Breaking a lot of my code that puts
pathnames by pasting together file and directory entries from environment 
variables (exported by a parent process).

I thought only the first double-slash was significant in cygwin32.

Mumit
-
For help on using this list, send a message to
"gnu-win32-request AT cygnus DOT com" with one line of text: "help".

- Raw text -