From: ertung AT ponder DOT csci DOT unt DOT edu (ERTUNG BORA) Message-Id: <9609201747.AA09431@ponder> Subject: Re: 1 bug(?) open/readdir & glob To: grendel AT ananke DOT amu DOT edu DOT pl (Mark Habersack) Date: Fri, 20 Sep 1996 12:47:04 -0500 (EDT) Cc: djgpp AT delorie DOT com In-Reply-To: from "Mark Habersack" at Sep 20, 96 03:28:07 pm Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1293 > > On Thu, 19 Sep 1996, ERTUNG BORA wrote: > > >Hi, > > > >readdir works fine, but there is definitely something wrong with > >findfirst/findnext functions of djgpp. These two function works really > >terrible. However, you can use opendir/readdir functions to read the > >current directory. > What's so terrible about find...? The only problem with them is the famous > bug with cutting off first two letters of filename (if anyone asks about it > again I think I'll go puke) Then go head and puke, who cares. When I use findfirst/findnext,some of my local and global variables are also corrupted by these two functions. Indeed, I havent committed that bug that you told in your posting. > In djgpp it really doesn't matter whether you'll use findfirst/findnext or > readdir. readdir() uses find... anyway. Yes, It doesnt matter , but the problem is why you mentioned about it. > > ********************************************************************** > So if you ask me how do I feel inside, I could honestly tell you we've > been taken on a very long ride. And if my owners let me have free time > some day, with all good intention I would probably run away! > Clutching the short straw... > ******************* http://ananke.amu.edu.pl/~grendel **************** > >