Message-ID: <00da01c152a0$3a22f8e0$845824d5@zephyr>
From: "Eric Botcazou" <ebotcazou AT libertysurf DOT fr>
To: "DJGPP workers" <djgpp-workers AT delorie DOT com>
References: <10110111847 DOT AA16991 AT clio DOT rice DOT edu>
Subject: Re: _findfirst() patch
Date: Thu, 11 Oct 2001 23:57:21 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2014.211
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2014.211
Reply-To: djgpp-workers AT delorie DOT com

> You had asked about the question of when our internal findfirst
> closes the handle for you because there were no wild cards.
> In that case _findclose would be able to recognize it as already
> being closed and do nothing.

I was thinking of the other case for which the handle is automatically
closed: when findnext() doesn't find any more files, it closes the handle.
This behaviour could potentially break the example I gave, if _findfirst()
was living on top of findfirst().

> This may be the best fix.  I believe Eli also said this might be the way
> to go.  However, it depends on how much time and effort you are willing to
> spend.  I personally would not object to putting your current versions
> into the the library.

I don't think that coding it would require me to spend more than six nights
at a stretch on my keyboard, and given that my limit is seven... ;-)

--
Eric Botcazou
ebotcazou AT multimania DOT com