From: sandmann AT clio DOT rice DOT edu (Charles Sandmann)
Message-Id: <10108151427.AA15427@clio.rice.edu>
Subject: Re: _open.c development dif - Win2000 hacking
To: eliz AT is DOT elta DOT co DOT il
Date: Wed, 15 Aug 2001 09:27:25 -0500 (CDT)
Cc: djgpp-workers AT delorie DOT com
In-Reply-To: <557-Wed15Aug2001094031+0300-eliz@is.elta.co.il> from "Eli Zaretskii" at Aug 15, 2001 09:40:31 AM
X-Mailer: ELM [version 2.5 PL2]
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Reply-To: djgpp-workers AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk

> Sorry, I'm probably missing something, because I cannot figure out
> where do [fstat _open] failures happen.  Can you elaborate, and perhaps show
> some code fragments and error messages?

I printed the file names causing failure, and got "/etc/localtime" and
"/djgpp/zoneinfo/GMT".  Time stuff that fstat calls.  Unrelated.

> > One thing I need to know - how do people use the directoryname/nul detection
> > to determine if a directory exists?
> 
> I don't think you need to worry about that: no code I know of uses
> this to test for an existing directory.  It's normally either `stat'
> or `access (..., D_OK)', but not directory/nul.

We should be in good shape then.