|
![](/i/fill.gif) |
In article <3A186246.8AFA7CBC@alpharay.de>, Paul Blaszczyk
<3d### [at] alpharay de> wrote:
> what you think about implementing of macros directly in POV
> source-code??
> I don't mean every small macro, i mean the famous macros, like the
> hair-macro and the tree-macros. Theese will be much faster in the source
> as an POV-macro.
More work than it is worth, and it would break consistency with the rest
of the POV language. If those things are added as POV features, they
should be modified to use the correct syntax. For example, trees should
be objects, not functions, POV keywords should all be lower-case, etc...
Also, it would be a tremendous amount of work to simply convert the more
complex macros and includes into functions.
BTW, for a lot of my patches, I do prototyping in POV-Script and then
use that as a base for the actual patch. The particle_system patch was
descended from a simple particle system written in POV-Script, the
extended blur patch I am now working on has it's algorithms being tested
in .pov files, etc...
Also, some features were originally macros, for example, the "sgn()"
function in MegaPOVPlus.
--
Christopher James Huff
Personal: chr### [at] mac com, http://homepage.mac.com/chrishuff/
TAG: chr### [at] tag povray org, http://tag.povray.org/
<><
Post a reply to this message
|
![](/i/fill.gif) |