"Tim Hamza" <tim### [at] frontier net> wrote in message
news:3dd28730@news.povray.org...
>
> StatLn30="Time For Parse: 0 hours 0 minutes 1.0 seconds (1 seconds)"
> StatLn31="Time For Trace: 0 hours 31 minutes 34.0 seconds (1892
> seconds)"
> StatLn32=" Total Time: 0 hours 31 minutes 33.0 seconds (1893
> seconds)"
Weird. Don't have clocks that run backward at home, do you? Only joking. I'm
going to be paying closer attention to the times now. If it happens on this
typical single CPU computer too maybe it's something amiss in the way the
program handles that. But if a really rare occurance then no one might ever
see this happen too. Maybe Chris Cason knows how the timings could have
gotten buggy since he added a CPU counter too. Just might be too obscure a
thing going on too though, not like it's doing much but slipping up a digit.
--
Farewell,
Bob
Post a reply to this message
|
