Date: Sun, 15 Jun 1997 12:07:06 +0300 (IDT)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To: Vik Heyndrickx <Vik DOT Heyndrickx AT rug DOT ac DOT be>
cc: djgpp AT delorie DOT com
Subject: Re: Why are these unix like paths searched?
In-Reply-To: <339FFB9E.2E41@rug.ac.be>
Message-ID: <Pine.SUN.3.91.970615120638.14561N-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Precedence: bulk


On Thu, 12 Jun 1997, Vik Heyndrickx wrote:

> Some are even not valid DOS names (go32/2.7.2.1/include).

You forget Windows 95, where such names *are* allowed.

> This may be a wise thing to do under a unix
> environment, but under dos this seems to me just a waste of clock
> cycles?

The waste of cycles only happens when you include a non-existing
header or gcc tries to call a non-eisting executable.  Since DJGPP.ENV
sets things up so the *real* include directories are searched *before*
the default, a header will always be found in one of them, and you
don't get to the non-existent ones.

I also fail to see why do you think this behavior is more appropriate
on Unix than it is on DOS/Windows.  If you don't have "/usr/local/bin"
on a Unix system, why is it reasonable to look for it?