From: sam AT greenaum DOT demonARSE!ARSE!ARSE!.co.uk (Sam.)
Newsgroups: comp.os.msdos.djgpp
Subject: Are there any problems with findfirst() findnext()
Date: Mon, 16 Nov 1998 02:22:15 GMT
Organization: Rossum's Universal Robots
Message-ID: <36508be1.9756460@158.152.254.70>
NNTP-Posting-Host: greenaum.demon.co.uk
X-NNTP-Posting-Host: greenaum.demon.co.uk:194.222.71.189
X-Trace: news.demon.co.uk 911182939 nnrp-06:28152 NO-IDENT greenaum.demon.co.uk:194.222.71.189
X-Complaints-To: abuse AT demon DOT net
X-Newsreader: Forte Agent 1.5/32.452
X-No-Archive: yes
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Lines: 13
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

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?


------------------------------------------------------------------------

The person who said he was a crap presenter knows nothing because compared
to the outwardly camp stuart miles, speech impediment Katy Hill and nothing
upstairs Konnie Huq, he was a true professional. Heh heh heh.