In article <Xns### [at] 204213191226>,
 "Rafal 'Raf256' Maj" <raf### [at] raf256com> wrote:

> This is a very good idea, but with one disadvantage - if someone realy 
> needs i.e. path and some features from 3.5 - and he have to choose one of 
> them.

If they know the basics of how to program (and have the tools), they 
could make their own version. Otherwise they will have to wait for 
someone else or find a workaround.


> Maybe put togeather most up-to-date patches into POV 3.6 and release it as 
> very untested and unstable version for beta tests ? Then lots of work in 
> testing and maybe documentation, examples, includes can be done by users :)

No. Stupid, idiotic idea. No, no, no. It can be guaranteed that this 
will not happen.
This is what MegaPOV and similar patch collections are for, to give 
patches a place where they can develop and be refined to the point where 
they are something useable for an official version. And making an 
official version takes a lot of work, making sure there are no conflicts 
or redundancies, working out the best syntax and internal design, and 
then lots of testing before it is even suitable for public beta.

Suggesting that the POV Team just hack something together with no regard 
to the future is just insulting.

-- 
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