Date:	Mon, 16 Nov 1998 10:40:54 +0200 (IST)
From:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender:	eliz AT is
To:	djgpp AT delorie DOT com
Subject:	Re: Are there any problems with findfirst() findnext()
In-Reply-To:	<36508be1.9756460@158.152.254.70>
Message-ID:	<Pine.SUN.3.91.981116104036.7241M-100000@is>
MIME-Version:	1.0
Reply-To:	djgpp AT delorie DOT com

On Mon, 16 Nov 1998, Sam. wrote:

> I've written a program that so far just loops through a directory and
> outputs the names of files fitting the specifier, using findfirst()
> and findnext(). This is under Windows 95. If I set LFN=y, I only get
> the first filename (ie, findnext() doesn't work), if I set LFN=n I get
> all the filenames, but the short versions. Is there something I should
> be aware of?

This is most probably some bug in the way you use findfirst/findnext.
They both work in LFN and non-LFN mode alike.  If you want to convince
yourself, try using opendir and readdir, they call findfirst and
findnext internally.

If you cannot figure this out, post a short program which exhibits the
problem on your machine, and somebody will find the cause.

- Raw text -