Felix Wiemann wrote:
> 
> > The modeller should take care of this itself.
> 
> An if it doesn't? :)

Don't blame POV-Ray.

> Of course it's not clear what's the resulting object, but why not
> dropping it *with a warning*, so the user is noticed that something may
> go wrong? What's the problem with that? Isn't that better than stopping
> with an error?

Having no object may cause secondary problems.  What if the the code uses
things like trace() or min/max_extend() and relies on reasonable results?

Christoph

-- 
POV-Ray tutorials, IsoWood include,                 
TransSkin and more: http://www.tu-bs.de/~y0013390/  
Last updated 20 Apr. 2002 _____./\/^>_*_<^\/\.______

Post a reply to this message