> Personally I felt it was worth sacrificing simplicity for speed, particuarly
> considering how the mesh creation macros might be used.  There may well be a
> case for allowing both options, so that users who want to quickly write a
> mesh creation macro for, say, a still scene can do so without worrying about
> the full coding.  And maybe raising the above parsing performance issues in
> povray.programming could lead to a patch that eliminates speed concerns
> altogether (hint, hint!)?

God save me, but I'm working on it.  At the moment it seems to be
executing properly.  I need to clean up the code and test it in various
alignments, but it was possible with minimal code involvement.

In my Linux, the example that Chris gave is only marginally faster when
the macro is hand-expanded.  Afterwards, I don't notice any difference
at all.

I should be satisfied in a few hours that it works properly and will put
a patch somewhere.  As I don't run any patched POV-Ray, I don't know how
well it will merge with them!

Post a reply to this message