time.clock() or Windows bug?

[Theo v. Werkhoven]

The carbonbased lifeform Tim Roberts inspired comp.lang.python with:
> Nick Craig-Wood <nick at craig-wood.com> wrote:
>>
>>Hmmm, 10,000,000 cycles (40 ms @2.5GHz) is nowhere near the ~90,000
>>second jump in time.clock() output reported by the OP.  I wonder if
>>there could be a different cause?
>
> Just wild theorizing, but it's possible that they are actually getting a
> negative delta, and some kind of signed/unsigned manipulation produces the
> 90,000 number.

Actually, in previous runs I /did/ see negative timestamps using 
time.clock().
Bizar.

Theo
-- 
theo at van-werkhoven.nl    ICQ:277217131                      SuSE Linux
linuxcounter.org: 99872  Jabber:muadib at jabber.xs4all.nl  AMD XP3000+ 1024MB
"ik _heb_ niets tegen Microsoft, ik heb iets tegen
 de uitwassen *van* Microsoft"