Scott Gammans wrote:
>>There is no point in trying to investigate in a problem if it does not
>>exist in the current code.
> 
> 
> Could you please explain that statement? If there is a problem in the
> binaries that are out in the field, what good is it to test a reported bug
> in your development code (source code to which common users do not have
> access)? Sure, it proves that the next version of POV-Ray won't have the
> problem, but until *we* have the new version, it doesn't do us users much
> good, does it?

The current code is more or less what will be the next official version 
that will be released.  It does not suffer from the problem so this is 
as much as what can be done for the users.  Looking into the 3.5 code to 
find the original problem will not change anything about this - you will 
still have to wait for the next release to have this fixed in official 
POV-Ray.

If we now all start looking where exactly the problem is and how it 
could be fixed although it already is this would only delay work on the 
next POV-Ray version - i don't think this is in the interest of you or 
any other user.

Christoph

-- 
POV-Ray tutorials, include files, Sim-POV,
HCR-Edit and more: http://www.tu-bs.de/~y0013390/
Last updated 25 Oct. 2003 _____./\/^>_*_<^\/\.______

Post a reply to this message