POV-Ray : Newsgroups : povray.newusers : max(0,min(1,x)) : Re: max(0,min(1,x)) Server Time
5 Sep 2024 00:14:10 EDT (-0400)
  Re: max(0,min(1,x))  
From: Christopher James Huff
Date: 2 Oct 2002 14:06:03
Message: <chrishuff-386950.14031802102002@netplex.aussie.org>
In article <Xns### [at] 204213191226>,
 "Rafal 'Raf256' Maj" <raf### [at] raf256com> wrote:

> Maybe isosurface using only one clip() in it's pattern ?

It'd either be so fast it wouldn't matter or the clip would take such a 
small fraction of total evaluation time you wouldn't notice a difference.

You really seem to have no idea how optimization is done...you optimize 
slow parts, not simple parts. The clip() function is likely to take only 
a very tiny amount of total rendering time, and then in only a small 
percentage of scenes. It would be a waste of time to implement it 
internally, the time would be better spent with other optimizations, 
maybe something like allowing inlining of functions, where POV would 
expand a clip() call to the min/max() calls. Or more powerful macros.

-- 
Christopher James Huff <cja### [at] earthlinknet>
http://home.earthlink.net/~cjameshuff/
POV-Ray TAG: chr### [at] tagpovrayorg
http://tag.povray.org/


Post a reply to this message

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