home *** CD-ROM | disk | FTP | other *** search
- Xref: sparky comp.os.msdos.4dos:18 comp.os.msdos.programmer:8521
- Path: sparky!uunet!cs.utexas.edu!news
- From: phil@cs.utexas.edu (Philip Smolen)
- Newsgroups: comp.os.msdos.4dos,comp.os.msdos.programmer
- Subject: Re: Patches to make BC++ 3.0 generated code 4DOS-aware
- Date: 13 Aug 1992 14:01:18 -0500
- Organization: U Texas Dept of Computer Sciences, Austin TX
- Lines: 25
- Distribution: inet
- Message-ID: <l8lcbuINNh32@muleshoe.cs.utexas.edu>
- References: <1992Aug08.180127.23394@donau.et.tudelft.nl> <b8zmck_.messina@netcom.com> <Bsq3rs.Dz0@wpi.WPI.EDU>
- NNTP-Posting-Host: muleshoe.cs.utexas.edu
- Keywords: 4DOS, C, BC++ 3.0, setargv
-
- In article <Bsq3rs.Dz0@wpi.WPI.EDU> nyh@wpi.WPI.EDU (Nevo Y Hed) writes:
- >>findfirst() and findnext() have nothing to do with the shell. They
- >>are DOS interrupts (21/4E & 21/4F, respectively). Unless you are
- >>willing to invoke shell to search for each file, which would be
- >>pathetically slow, there is nothing JP Software can do for you.
- >>You may use FCBs if you wish, they're faster... not any better though.
- >
- >BorlandC has it's own, non-dos findfirst find-next. I didn't do any
- >reading on the difference.
- >
-
- That's not quite correct. I was just looking at the source
- code for firstfirst, findnext, _dos_findfirst, _dos_findnext.
- Each one makes calls to the appropriate dos call (21/4e or
- 21/4f). The only thing that they do on top of that is set
- the DTA, restore the DTA, and translate the error message.
- The only difference between the _dos_find's and the find's
- is that they call different functions to translate from DOS's
- error code to their own return values.
-
- I don't know why they use different structure definitions
- for the two types of functions. They pass each structure
- directly to DOS, then directly back to the caller.
-
- --Phil
-