 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Hi,
With POV-Ray for Windows v3.0 and v3.1 this works:
sphere {
0, 1
texture {
#declare X = texture { pigment { color rgb <1, 0, 0> } }
#declare Dummy = 1234;
X
}
}
This doesn't work - it causes an error like "Missing pigment"
sphere {
0, 1
texture {
#declare X = texture { pigment { color rgb <1, 0, 0> } }
X
}
}
Bye,
Friedemann
Friedemann Schmidt
F.S### [at] fhtw-berlin de
Raytracing-Gallery: http://www.rz.fhtw-berlin.de/~s0049669/
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
It appears to me the problem is that the parser believes you
are defining a recursive compound texture..... butted
textures after a #declare are grouped.
So this may be a fundamental weakness in the syntax rather than
a bug in the implementation.
This should also "fail" :
sphere {
0, 1
#declare X = texture { pigment { color rgb 1 } }
texture { pigment { color rgb 0 } }
}
The solution to this is for ALL "#" directives be semicolon terminated,
or at least all #declares..... I wonder why this wasn't done?
Dan
Friedemann Schmidt wrote:
>
> Hi,
>
> With POV-Ray for Windows v3.0 and v3.1 this works:
>
> sphere {
> 0, 1
> texture {
> #declare X = texture { pigment { color rgb <1, 0, 0> } }
> #declare Dummy = 1234;
> X
> }
> }
>
> This doesn't work - it causes an error like "Missing pigment"
>
> sphere {
> 0, 1
> texture {
> #declare X = texture { pigment { color rgb <1, 0, 0> } }
> X
> }
> }
>
--
http://www.flash.net/~djconnel/
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
I believe there was talk of doing exactly that. But then "small" changes
are easier to implement than "large". Not just for the program but the
USER.
--
regards
Nathan O'Brien
no1### [at] no13net
http://www.no13.net
Dan Connelly wrote:
>
>
> The solution to this is for ALL "#" directives be semicolon terminated,
> or at least all #declares..... I wonder why this wasn't done?
>
> Dan
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Nathan O'Brien wrote:
>
> I believe there was talk of doing exactly that. But then "small" changes
> are easier to implement than "large". Not just for the program but the
> USER.
Not always.... surgery is usually best done in one session.
There are arguments on both sides.
Dan
--
http://www.flash.net/~djconnel/
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
