Christoph Hormann wrote:

> 
> Le Forgeron wrote:
 
> And the macro would just have to analyze the components of the vectors and
> place 'Vector.t' at the appropriate positions in the poly object.  I
> currently don't have the time to write it, but it's really quite easy
> (although it would take some time to parse for a 15th order poly).  


Please, do not waste your time at writing such kludging-macro, when the 
best solution would have been to change the syntax of the poly objects
so as to parse only the useful information. At worst, if backward 
compatibility is an issue, a new 'poly2' syntax would be able to provide 
the new one while the old 'poly' remained unchanged. (just like the new 
mesh2... same core object, different syntax!)

Post a reply to this message