|
![](/i/fill.gif) |
> and if you add some "(" and ")" ???
> either in the macro itself, before the "#if" and after the first "#end"
> or around the "POS(5)" ...
>
> I for myself try to include such macros always in parentheses to avoid
> side-effects... maybe this is one to the parser ...
>
Yes, I discovered that shortly after. But in a more complex example, this
wouldn't be so obvious. The current behaviour is at least confusing :) I hope
there will be some change to the parser, so it either gets more strict in what
it accepts, or everything accepted also gets handled correctly..
--
#macro C(X,Y)cylinder{X*x<X,0,-Y/2>.1}#end#macro U(R,X,Y)intersection{torus{.9
.1}box{-1 0rotate y*R*90}translate<X,0,Y>scale 1-z*.5}#end union{U(0,0,0)U(1,0
,0)U(2,-1,-1)U(1,1,0)U(1,1.5,-3)U(1,2,0)U(3,1,0)U(2,2,0)U(0,3,0)U(3,2,.5)C(.1,
2)C(.8,1)C(.8,-1)C(1.1,1)C(1.9,-1)pigment{rgb 10}rotate x*90translate<-1,0,4>}
Post a reply to this message
|
![](/i/fill.gif) |