William F Pokorny <ano### [at] anonymousorg> wrote:
> On 4/18/20 4:12 PM, jr wrote:
> > ... the problem is/was the range of float not being enough.
> Not trying to be flippant, but I think it does when it does, and doesn't
> when it doesn't. It's a judgement.
> The scale and range of a scene with respect to accuracy as an issue is
> always there relative to the accuracy you have available.
naively, I'd assumed some kind of upgrade/development "policy" that sees all
floats replaced with doubles, in time.
> Relatedly, I believe in going after better performance continually in
> software tools - otherwise you're on the slippery slope to poky. :-)
hmm, I probably "sit on the fence" on that. eg agree with you when it's a
compiler or other s/ware which has to take h/ware developments into account, but
kind of disagree for, say, programs not tied to h/ware, like 'sed'.
Post a reply to this message