![](/i/fill.gif) |
![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
It may also cause problems if you use it in odd places, like:
sphere { <1,2,3>, # a = 1 2 pigment { rgb 1 } }
You may think that it's an unrealistic example, but it isn't.
One word: Macros.
--
main(i,_){for(_?--i,main(i+2,"FhhQHFIJD|FQTITFN]zRFHhhTBFHhhTBFysdB"[i]
):_;i&&_>1;printf("%s",_-70?_&1?"[]":" ":(_=0,"\n")),_/=2);} /*- Warp -*/
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
Chris Huff wrote:
>It might allow simplifying the parser to allow faster parsing,...
Ah, ok.
>... and provides a visually obvious cue to the end of the statement(which
>can be several lines and several {} blocks down, like in the case of
>layered textures).
Personaly I don't need or like them for that, I forget to put them in very
often and pov runs ok, except for the warnings.
Ingo
--
Photography: http://members.home.nl/ingoogni/
Pov-Ray : http://members.home.nl/seed7/
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
In article <39b505ca@news.povray.org>, Warp <war### [at] tag povray org>
wrote:
> It may also cause problems if you use it in odd places, like:
>
> sphere { <1,2,3>, # a = 1 2 pigment { rgb 1 } }
You mean not using a semicolon will cause problems, right? Because I
don't think a "# VarName" feature would cause trouble.
--
Christopher James Huff
Personal: chr### [at] mac com, http://homepage.mac.com/chrishuff/
TAG: chr### [at] tag povray org, http://tag.povray.org/
<><
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
ingo wrote:
> Personaly I don't need or like them for that, I forget to put them in very
> often and pov runs ok, except for the warnings.
When semi-colons were first introduced I bitched up a storm about
them. They are particularly bad in the windows version if you have
"message stream to consol" turned on because all of the warning
messages chew up cpu cycles like there's no tomorrow. I finaly
broke down and forced myself to use them and it has become almost
second nature to use them now. I could do without them but if
the parser runs better with them I can live with that.
--
Ken Tyler - 1400+ POV-Ray, Graphics, 3D Rendering, and Raytracing Links:
http://home.pacbell.net/tylereng/index.html http://www.povray.org/links/
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
Chris Huff <chr### [at] mac com> wrote:
:> It may also cause problems if you use it in odd places, like:
:>
:> sphere { <1,2,3>, # a = 1 2 pigment { rgb 1 } }
: You mean not using a semicolon will cause problems, right? Because I
: don't think a "# VarName" feature would cause trouble.
That was what I meant. If you don't use a semicolon, the parser may get
confused.
--
main(i,_){for(_?--i,main(i+2,"FhhQHFIJD|FQTITFN]zRFHhhTBFHhhTBFysdB"[i]
):_;i&&_>1;printf("%s",_-70?_&1?"[]":" ":(_=0,"\n")),_/=2);} /*- Warp -*/
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |