"Chambers" <ben### [at] pacificwebguycom> wrote in message 
news:49cd21cc$1@news.povray.org...
>
> In fact, if that's the case then the current parser could be kept for 
> backwards compatability, activated by an appropriate #version directive 
> (or whatever the equivalent would be in the new language) but remain 
> static and disallowing access to features exclusive to the new language.
>

This would make a lot of sense, at the very least as a transition strategy. 
Otherwise the cutover is likely to leave most of the existing community 
using the scene files, macros and utilities that they know work with the old 
software and a small new community that learns the new software.

Having such a transition would permit teething problems with the new 
unproven approach to be ironed out and omissions, where the new software 
can't do all that the old software did, to be bridged. It would also allow 
time for a reasonable proportion of the assets developed for POV-Ray to be 
migrated across. A process that won't really even be able to start in 
earnest until V4 is demonstrably stable (unless of course we build 6 years 
of Beta testing in the plan :-)).

Regards,
Chris B.

Post a reply to this message