"Thorsten Froehlich" wrote:
> You intentionally "break" the comparison operator.

Yes. But comparison operators are often broken by coders unintentionally.
The initial_clock keyword could easily be involved in a long series of
calculations which for each new calculation gets a little more imprecise.

When you have an animation with one object moving in a specific way and you
see a bug in the behaviour that changes from frame to frame, and there are
100 different places the bug could origin from, the first thought that comes
to your mind is not exactly the initial_clock value, which should be exactly
the same in every frame. An initial_clock value that has small variations
from frame to frame thus makes debugging much more difficult than needed be.

I must again refer to the fact that the current initial_clock value in
POV-Ray is indeed the same in every frame. Even if it's imprecise, it's the
*same* imprecise value in every frame, as one would expect. Why do you want
to take that away in favour of a worse solution where there are small
changes from frame to frame?

Rune
--
3D images and anims, include files, tutorials and more:
Rune's World:  http://rsj.mobilixnet.dk (updated Feb 16)
POV-Ray Users: http://rsj.mobilixnet.dk/povrayusers/
POV-Ray Ring:  http://webring.povray.co.uk

Post a reply to this message