Jan Skibinski <[EMAIL PROTECTED]> writes: > Any good idea? First prize: a bottle of something good. :-) The easiest ought to simply have enough granularity in the gettimeofday() or equivalent. Sure you can guess the approximate time in hours or seconds, but can you guess it in micro- or nanoseconds? (Is there a clock cycle counter on modern CPUs? That would give you ns resolution, on modern hardware). Modern motherboards also have temperature and voltage sensors - although I don't know if the granularity is good enough. -kzm -- If I haven't seen further, it is by standing in the footprints of giants
- Re: When is it safe to cheat? Lennart Augustsson
- RE: When is it safe to cheat? Erik Meijer
- Re: When is it safe to cheat? Fergus Henderson
- When is it safe to cheat? Frank Atanassow
- Re: When is it safe to cheat? Fergus Henderson
- Re: When is it safe to cheat? Fergus Henderson
- Converting float to double. Ronald J. Legere
- Re: When is it safe to cheat? Jan Skibinski
- Re: When is it safe to cheat? Keith Wansbrough
- Re: When is it safe to cheat? Jan Skibinski
- Re: When is it safe to cheat? Ketil Malde
- Re: When is it safe to cheat? Frank Atanassow
- Re: When is it safe to cheat? Jan Skibinski
- Re: When is it safe to cheat? Michael Hobbs
- Re: When is it safe to cheat? Sverker Nilsson
- Re: When is it safe to cheat? Fergus Henderson
- Re: When is it safe to cheat? Ketil Malde
- Re: When is it safe to cheat? Sverker Nilsson
- Re: When is it safe to cheat? Bjarke Dahl Ebert
- Re: When is it safe to cheat? Michael Hobbs
- Re: When is it safe to cheat? Ketil Malde