LambaMOO implements comments in an unusual way, seemingly not as a section marked 'don't execute' but as a string whose value is unassigned to any variable or operation and is discarded instead:
"I'm sure you are all aware that it looks like this.";
It looks to me that this is a consequence of the server's method of compiling the code upon entry and discarding the source: no comments would survive this process intact unless they were evaluated. But this must have some cost in terms of execution time, mustn't it? Every evaluation must take some processor cycles, and therefore comment-ridden code would be: how much slower than commentless code?
As soon as I read of this implementation I acquired my early habit of not commenting my code, not liking the idea of taking such a hit. Was my fear justified. I also know that I can use /* C-style comments */ so long as I preserve the text files my code is stored in, and such comments will not even get stored in the database (which conserves both processor and memory resources). This is what I have been doing as my codebase has burgeoned. But I've still always wondered how much of hit database-stored comments cause...
tM
############################################################# This message is sent to you because you are subscribed to the mailing list <[EMAIL PROTECTED]>. To unsubscribe, E-mail to: <[EMAIL PROTECTED]> To switch to the DIGEST mode, E-mail to <[EMAIL PROTECTED]> To switch to the INDEX mode, E-mail to <[EMAIL PROTECTED]> Send administrative queries to <[EMAIL PROTECTED]>
