POV-Ray : Newsgroups : povray.general : Doc bug - substr() : Re: Doc bug? #range - not a doc bug. Server Time
8 Aug 2024 12:26:33 EDT (-0400)
  Re: Doc bug? #range - not a doc bug.  
From: Geoff Wedig
Date: 23 Feb 2001 11:32:32
Message: <3a9690a0@news.povray.org>
Warp <war### [at] tagpovrayorg> wrote:

> Geoff Wedig <wed### [at] darwinepbicwruedu> wrote:
> :> Are you sure clock is an integer?

> : Well, initial_clock and final clock are both integers, and equal to initial
> : frame and final frame respectively.  And in the log they're all .00000, so
> : yeah, pretty sure. ;)

>   It may (seem to) have an integer value, but that doesn't mean that it's
> an integer type.
>   As all values in povray, it's a floating point value. It shouldn't be
> necessary to say more...

Except for the slight problem that floats can represent integers, the
initializers and additions are integers.  There's absolutely no reason why
these wouldn't be integers too.  Or are you saying that Pov gets numerical
error when adding 1 succesively to 0 for values < 100?  If so, then POv has
far worse problems than the range statement.

Geoff


Post a reply to this message

Copyright 2003-2023 Persistence of Vision Raytracer Pty. Ltd.