From:	Eric Backus <ericb AT lsid DOT hp DOT com>
Subject:	Re: The continuing saga of getcwd()
To:	djgpp AT sun DOT soe DOT clarkson DOT edu (djgpp)
Date:	Wed, 30 Jun 93 11:18:56 PDT
Mailer:	Elm [revision: 66.25]

It is true that we've already spent too much time on this tiny little
problem, but I'll contribute a little more to this discussion anyway.

I was the one who suggested that UNIX programs might possibly break if
there was a DOS drive specifier returned by getcwd().

After some thought, I would nevertheless vote that getcwd() should
return the DOS drive specifier.

My reasoning is:

	1. I have searched quite a lot of UNIX source code, and I can
	   find no cases where the UNIX code would be broken.  (Can
	   anyone find even ONE example?)

	2. Others have posted that they have DOS programs that DO
	   break with the current behavior of getcwd().

	3. A "DOS aware" unix program may need some way to figure out
	   the current DOS drive, and I can think of no better method
	   of doing this than parsing it from getcwd().

Just add it; no one will even know the difference.
--
				Eric Backus
				ericb AT lsid DOT hp DOT com
				(206) 335-2495

- Raw text -