PE>                 fgets on text files
 PE>                 -------------------
 PE>                 
 PE> bcc - 14.4, 13.8, 14.1
 PE> gcc - 13.6, 13.5, 13.3
 PE> icc - 8.2, 8.4, 8.2
 PE> wcc - 24.6, 24.6, 24.6
 PE> pbcc - 5.4, 5.4, 5.3
 PE> pgcc - 4.9, 4.9, 4.9
 PE> picc - 5.4, 5.3, 5.3
 PE> pwcc - 5.4, 5.4, 5.5

 PE> summary - cset has the best library, watcom the worst.  pdpclib

...not the best/worst library --- the best/worst fgets().


Try the same type of program with fseek()/fread() --- IBM's sucks big time
-- it does a DosBufReset() everytime!

 PE> creams the lot.  gcc is the best compiler.

Does pdpclib handle crlf cooking?  Is it thread safe?  I know ibm &
watcom do, which is bound to add overhead.

Are you ensuring that each CRT is using the same size FILE* buffers?

 PE>                 large freads on binary files
 PE>                 ----------------------------

oops -- I guess you did try it.

 PE> summary - Borland has the best library, cset has the worst.
 PE> pdpclib creams the lot.  The compilers are equal.

Same questions (I know crlf cooking is not often used by fread/fwrite, but
it is supported by the others).


 PE> I used a 486DX33 with a RAM disk in order to perform these tests,

HPFS, with lazy writes,  is often (actually,  most of the time) faster for
such tests than \os2\vdisk.sys.


Btw -- why go to so much trouble writing a library that already comes with
each compiler?


--- Maximus/2 3.00