MK> The following code was compiled with VisualAge C++ and run through the
MK> profiler.  No calls to DosSubSet were traced.  DosWrite consumed 99%
MK> of runtime, DosClose 1%, DosOpen was the only other function traced.

Does VisualAge C++ have the ability to tell you which lines of
a function are the most heavily hit too?  At the moment I have
Borland, which has no profiler, EMX 0.9 which has no profiler,
CSET++ which has a good profiler except that it only takes me
to a function level, and if I want to know more than that I have
had to create a dummy function.  :-(  Then I have Watcom C++ which
will tell me the lines that get hit the most (although from memory,
even that varies wildly for no apparent reason), but as far as the
big picture is concerned, it gets the OS functions grossly incorrect.  
Is there any compiler besides VisualAge C++ that has a competing 
profiler?  BFN.  Paul.
@EOT:

---