// vs. /**/

bad joke.

in any case, i prefer // so i can comment off large chunks of things without the stupid */ ending the comment before i want.

Yeah I know, I just wondered how other vs. posts could make it to two pages.

Not being able to nest the /* comments is the most annoying thing ever too.

When you make a binary exe the compiler removes all comments anyhow. It has no effect in that scenario.

*xgkkp blinks*

// comment


/* Comment that is very long. So long, in fact, that in order
   to present it correctly, it''s necessary to use several lines.
*/

#if 0
commented.out(code);
#if 0
which.can = be.nested; /* including comments */
#endif
but = must ? be : syntactically - correct;
#endif

---

How appropriate. You fight like a cow.

actually, I don''t think that it must be syntactically correct. Anything between an #if/endif preprocessor block that evaluates to false/0 doesn''t get included in the compilation proccess at all.

quote:

---

Original post by daerid
actually, I don''t think that it must be syntactically correct. Anything between an #if/endif preprocessor block that evaluates to false/0 doesn''t get included in the compilation proccess at all.

---

It has to fit the syntax of the preprocessor because the preprocessor still has to evaluate it. Granted, the preprocessor doesn''t understand all of C''s syntax, but a notable exception would be that it understands string literals. (#define''s don''t affect the content of a string literal) So, for instance, you have to at least make sure you properly nest your quote marks. Also think a backslash at the end of a line might cause problems, depending on the context.

As an alternative to trying to figure out if "/**/" or "//" is faster, consider optimizing away the entire comment.