> Ah, your macro enters a territory badly covered by the docs: creating 
a
> local variable with the name of a parameter... Dunno why it behaves 
the way
> it does, or why the +0 helps, though. At least it is not because of 
the
> MegaPOV: I tried it in 3.1g and it did the exact same thing. An easy 
thing
> to fix, though. Just use
> 
>     #local new_pos = ...
> 
> and later
> 
>     tree(new_pos...
> 

Thanks, I will use that. I wanted to avoid a new variable at first, but 
it's a lot better than the +0.

Elias Pschernig

Post a reply to this message