Re: Portable library to measure time
On Nov 1, 3:45 pm, "BGB / cr88192" <cr88...@hotmail.com> wrote:
"Julek" <julek...@go2.pl> wrote in message
news:90319dc1-1978-46f1-81f5-37937305da3e@z41g2000yqz.googlegroups.com...
Is there any simple library that can return a systemtime in
a resolution of max. 10ms, working on both Windows XP and
modern Linux? time() works on both but has a resolution of
1s. There is GetSystsmTime on Windows with 10ms resolution,
there are probably also some functions for Linux - but maybe
there is some library works on both these OSes?
don't use a library for what you can trivially do yourself...
That's ridiculous. You're job is to provide the best possible
solution at the lowest possible cost. Reinventing something
that is already available should only be done when there is a
very good reason for not using what is available. (Copyright
restrictions come to mind---some projects can't use GPL, for
example.)
using libs in this case does little more than create external
dependencies for which any potential users of said code may be
forced to deal with later.
If you're using a third party library, users never see it.
a lib is good if it is known to be commonly or near
universally available, is already in use of a project, or
represents a non-trivial amount of work, but otherwise I feel
use of libs is ill-advised, as it may create portability
issues (and people trying to dig around online to find "X
obscure library no one has heard of", or figuring out how to
do likewise by looking at the code and figuring out what the
API calls do...)..
now, maybe of some help:
#ifdef linux
...
gettimeofday(...);
...
#endif
or, maybe even:
#if defined(linux) || defined(__BSD__) || defined (__MACOSX__) || ...
...
gettimeofday(...);
...
#endif
And you say that using a lib will create portability issues?
What happens when you encounter a new OS? (And of course,
conditional compilation can quickly make the code completely
unreadable.)
my personal suggestion is to create a function, or maybe
collection of them, which provide a consistent interface to
OS-specific behaviors, and keep any OS specific parts confined
to these functions.
In other words, write a library that someone else has already
written.
Sometimes it's necessary---there can be a number of reasons not
to use an existing library. But you shouldn't rewrite it unless
it is necessary for some reason.
--
James Kanze