 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
> What *does* annoy me, however, is that the following, which should be
> perfectly fine:
>
> /* comment /* comment continued */
>
> gives an error, saying that the openings and closings of comments don't
> match. I think if nested comments aren't allowed, the program shouldn't
> complain about improper nesting.
Patient: It hurts when I do this.
Doctor: Stop doing that.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
In article <3cbe1353@news.povray.org> , "Slime" <noo### [at] hotmail com> wrote:
> /* comment /* comment continued */
>
> gives an error, saying that the openings and closings of comments don't
> match. I think if nested comments aren't allowed, the program shouldn't
> complain about improper nesting.
And how could it then determine if you want a part to be commented out or not?
If you think about what you are suggesting carefully you will find that what
you are expecting is mind-reading :-)
Thorsten
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"Warp" <war### [at] tagpovrayorg> wrote in message
news:3cbe163e@news.povray.org...
[snip]
> The great thing about nested comments being supported is that if
you
> have a piece of code with lots of /*...*/ comments and then you want
to
> comment out the entire piece of code, it works just fine.
This is exactly what I have always done since pov 2 in DOS. I'm new to
WinPov, wanted to play with 3.5 :) and wasn't aware of this codemax
error.
Alf
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
> > /* comment /* comment continued */
> And how could it then determine if you want a part to be commented out or
not?
> If you think about what you are suggesting carefully you will find that
what
> you are expecting is mind-reading :-)
Under my assumption that POV-Ray does not support nested comments, which has
been corrected, I would have expected it to behave like languages that
*don't* support nested comments, and simply ignore the second /*, since once
you're in a comment, the only thing that should be responded to is the
closing */.
- Slime
[ http://www.slimeland.com/ ]
[ http://www.slimeland.com/images/ ]
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
In article <3cbee3b7$1@news.povray.org> , "Slime" <noo### [at] hotmailcom> wrote:
>> > /* comment /* comment continued */
>
>> And how could it then determine if you want a part to be commented out or
> not?
>> If you think about what you are suggesting carefully you will find that
> what
>> you are expecting is mind-reading :-)
>
> Under my assumption that POV-Ray does not support nested comments, which has
> been corrected, I would have expected it to behave like languages that
> *don't* support nested comments, and simply ignore the second /*, since once
> you're in a comment, the only thing that should be responded to is the
> closing */.
Ah, so you had not seen Christoph Hormann's response which already noted that
nested comments are support just not in the editor. It is really hard to
figure out when you responded because of the wrong date in your posts. All
your posts are over six days older...
Thorsten
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
> Ah, so you had not seen Christoph Hormann's response which already noted
that
> nested comments are support just not in the editor. It is really hard to
> figure out when you responded because of the wrong date in your posts.
All
> your posts are over six days older...
Oops... you're right, I had my system clock set back a week. Strange.
I wonder why the newsgroup uses the time of the system that sent the
message? Seems that would cause errors with people in different time zones.
- Slime
[ http://www.slimeland.com/ ]
[ http://www.slimeland.com/images/ ]
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
In article <3cbf0c72@news.povray.org> , "Slime" <noo### [at] hotmailcom> wrote:
> Oops... you're right, I had my system clock set back a week. Strange.
>
> I wonder why the newsgroup uses the time of the system that sent the
> message? Seems that would cause errors with people in different time zones.
No, because posts include the time zone. As for why the user time is used,
well, that is Usenet history...
Thorsten
____________________________________________________
Thorsten Froehlich, Duisburg, Germany
e-mail: tho### [at] trfde
Visit POV-Ray on the web: http://mac.povray.org
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Slime <noo### [at] hotmailcom> wrote:
> Oops... you're right, I had my system clock set back a week. Strange.
Trying to trick the expiration code in POV-Ray? ;)
--
#macro N(D)#if(D>99)cylinder{M()#local D=div(D,104);M().5,2pigment{rgb M()}}
N(D)#end#end#macro M()<mod(D,13)-6mod(div(D,13)8)-3,10>#end blob{
N(11117333955)N(4254934330)N(3900569407)N(7382340)N(3358)N(970)}// - Warp -
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
> Well, in C you can do #if(0) ... #endif, but don't
> expect any editor to color that block as a comment.
<troll mode=short>
Vim does it perfectly. Another reason not to use emacs ? ;op
</troll>
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
> Trying to trick the expiration code in POV-Ray? ;)
I needed to render something really fast for a project, didn't have time to
redownload =) then I just never changed it back...
- Slime
[ http://www.slimeland.com/ ]
[ http://www.slimeland.com/images/ ]
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
