GW> Bit odd really, as the two compilers I've looked at so far say clock()
GW> measures time from program start.

It doesn't even do that. help-pc says it measures elapsed processor-time
for the process, so under an multitasking O/S it could well return a lower
value... (my turbo-c manual agrees) but clock under turbo-c 2.0 isn't
multitasker aware.

After some experimentation under linux, it appears that a clock counts only
the time that the process is actually executing, in a program that does a
sleep(10) (10 seconds) clock returns 0 (no time elapsed)

Two processes executing concurrently would share the "clocks" and
would each
only see half the elapsed time.

This suggests that the (portable) sleep in snippets is broken in that it
doesn't stop clock(). And that uclock is broken in that it doesn't measure
cpu-time.

I have no idea of what would happen under windows or OS/2 or on an Amiga or a
Mac.

                        

--- EzyQwk V1.20 01fa018d