Am 18.04.2010 21:44, schrieb H. Karsten:
> ok it's possible to run external code before and/or after the rendering in
> PovRay.
>
> What if having a syntax to run it from inside the script like a macro
>
> #declare Result=external_code_lua("Path/Name",Arguments)
> #declare Result=external_code_python("Path/Name",Arguments)
> #declare Result=external_code_php("Path/Name",Arguments)
> #declare Result=external_code_perl("Path/Name",Arguments)
> #declare Result=external_code_java("Path/Name",Arguments)
> #declare Result=external_code_bin("Path/Name",Arguments) (using stdout as
> return-value)
...
> Think of it: depending on the language using, you can make PovRay
> object-orientated!
>
>  From my personal taste, I would like to use Lua. It's designed to be used inside
> other programs, or scripts. It's object-orientated, fast, free, opencource (I
> think its MIT-License) and small.

Would there still be a big benefit in that, presuming the POV-Ray 4 SDL 
itself would be object-oriented and as fast as Lua or some such in the 
first place (which I consider a prime goal for POV-Ray 4)?

Post a reply to this message