Coridon Henshaw wrote:
> 
> This one is still present / back in part in Windows RC3 with regard to
> #macro names rather than functions.
> 
> Example scene:
> 
> #macro Center(obj)
> object {obj}
> #end
> 
> #include "shapes.inc"
> 
> Parsing fails on line 248 of shapes.inc when the Spheroid macro
> attempts to use 'Center' as a parameter name.
> 
> If this can't be fixed in the parser, could the standard includes be
> modified so their parameter names are all lower case (like all other
> Pov keywords) or otherwise mangled to reduce the chances of collisions
> with user macros?  Coming up with macro names that don't collide is a
> real headache as long as this bug is in place because so name good
> names are already wasted on macro parameters.

A consistent naming scheme will alleviate this problem.

For instance, I prefix vector names with a v, scalars with s,
index variables with i, and so on.

Regards,
John


-- 
Rusty is rendering!

Post a reply to this message