On 18 Dec 96  23:52:06, Marcel Vandevusse scribed in letters of flame on
the boiling sky:

 MV> Replying to a message of Vitus Jensen to Marcel Vandevusse:
 
 VJ> Timing your code under OS/2 isn't really possible because of the
 VJ> peemptive 
 VJ> multitasking.

 MV> It is when you're timing yout code at priority level 4 (server). Stops
 MV> the rest of the system dead in it's tracks. 

Er, sorry to disagree, but no, it doesn't. Unless some radical remodelling
has gone on since OS/2 2.11, priority class 4xx (foreground server) is not
the highest priority level.
Priority level 3xx *is* the highest; I've personally had experience of
running threads at 31F and locking myself (and all other processes) out of
the system.

If you haven't got the CPU clock meter (as I haven't; 486 only), there is
a nanosecond timer (982ns period I think) which is almost as good.

I tend to use gprof anyway. :)


... Out of paper reading drive I: (A)bort (R)etry (F)ail
--- Blue Wave/Max v2.30 [NR]