Date: Sat, 21 Sep 1996 15:32:02 +0200 (MET DST) From: Mark Habersack Reply-To: grendel AT ananke DOT amu DOT edu DOT pl To: ERTUNG BORA cc: djgpp AT delorie DOT com Subject: Re: 1 bug(?) open/readdir & glob In-Reply-To: <9609201747.AA09431@ponder> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Fri, 20 Sep 1996, ERTUNG BORA wrote: >> 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 I do care. No flames, please, it was just an expression (joke if you will ;-)) I guess I'll start putting [joke] label next to that kind of expressions. >and global variables are also corrupted by these two functions. Indeed, >I havent committed that bug that you told in your posting. Are you sure these two are causing the problem? Have you tried to convert the code to readdir()/opendir(). If with the latter two everything's OK then findfirst()/findnext() are not to be blamed for corrupting your vars. >> 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. Mentioned about what? About using readdir()/opendir(). In case you haven't read the former postings carefully enough, findfirs()/findnext() are in no way portable to/from Unix. They are DOS-specific and if you want to write portable code you have to avoid them. That's why I mentioned 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 ****************