Quote:
Originally Posted by Frankie
doesn't seem like a bug to me. just a bad use of comment codes. there's no reason why you should use the /* */ if you're just going to use // vice versa.
|
I just happened to close a commented line within the block comment when I added more information about the enclosed functions.
The script window telling you that the block comment is closed, but the compiler seeing it otherwise is a bug. And the fact that it only knocked out the serverside portion of the code is even worse...had nothing worked, I could have easily determined that the code was commented out, but that wasn't the case.
Quote:
Originally Posted by Tigairius
Anything after // will be comments, so you can't use */ after a // on the same line. Serverside is read separately from clientside, so if you did a /* at the top of a script, it would only comment out until it reaches //#CLIENTSIDE.
If you wanted to comment out a whole script you would have to put a /* at the top and a /* right under //#CLIENTSIDE.
|
Really?
If I placed /* at the top of a script, everything appears to be commented out in the script window (serverside AND clientside)...but I haven't tested if the clientside portion still works.
I know that // comments out the entire line, but it doesn't change the fact that the block comment appeared to be closed but in fact wasn't