From: Eric Marsden <eric.marsden@fr...> - 2007-05-19 10:21:15
On Unix platforms, GET-INTERNAL-RUN-TIME is implemented by calling
time(), so has a resolution of one second, which is not very
satisfactory in my opinion. Implementing this function using
gettimeofday() would allow a better resolution (such as a
millisecond), and I don't think that portability would suffer.
On win32, GET-INTERNAL-RUN-TIME is implemented using GetTickCount(),
so has good resolution. GET-INTERNAL-REAL-TIME is implemented using
times(), so has reasonable resolution.
From: Juan Jose Garcia-Ripoll <jjgarcia@us...> - 2007-05-21 18:33:26
I think I have finally fixed this issue today. It remains to test
whether the Windows ports are affected by the new changes.
Incidentally, there were resolution problems in GET-INTERNAL-RUN-TIME
which did not return the value in right units. The new implementation
uses getrusage() and gettimeofday() where available. Otherwise it
tries with times() and time(). On Windows, GetTickCount() is used and
get-internal-run-time returns the same value as
Thanks for pointing this out,
Facultad de Fisicas, Universidad Complutense,
Ciudad Universitaria s/n Madrid 28040 (Spain)