Warp <war### [at] tagpovrayorg> wrote in news:3cc34e42@news.povray.org:

From the fixed bugs section:

> * Function namespace problem
>   (Declared function names can't be used as macro parameter names. Might
>   not be possible to be fixed with the current parser. This is being
>   investigated.)
>   Reported in:
> function declaration and namespace
> http://news.povray.org/l2ji3uc2k9su99o2gct3n2thgqoq7f4pd5@4ax.com

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.

Post a reply to this message