I have seen many comments inside .c/.h codes while for search of my unsolved answers, and I have noticed that so fare all use this character // comments// for engine compiler to ignore it.
I understand if your using it for 2-3 lines of comments, but when it come to comments that take 10-15 lines of codes using this // for every line I find it to be a lot of unnecessary work.

So here is a little trick I came across that I'm sure most of you knew about it just in case someone didn't, it might make their explanatory comments(witch I appreciate so much) easier to work with:

use this before the comment /* then close it again before the last comment */. Don't leave any working code in between these characters /* function main()*/ your engine will ignore it.

small example:



Do make shore to close it after you open it, otherwise it will ignore entire code in your file.

I don't know maybe it looks cool or something just using these characters // for each line of comments. I'm all about simple and fast, I hope this helped someone out.

You got it wrong, it is supposed to be /* ... */

This is the common C comment, no magic

yes you are right sorry

The problem is that this type of comment isn't greedy but has lazy behavior, so once you have to comment out such a comment it gets pretty nasty...

this way of commenting doesn't support embedding comments into each other, besides most editors allow commenting/uncommenting a block with // instead of manually commenting each line.

I also hate the behavior, that the first */ leaves the "comment space"

This way its hard to quickly comment out a large codeblock when
there are "subcomments" with /* */ in it.

The last */ should determine the end of the commentblock.
But on the other hand this is a reliquia from the 70s,
and cant be changed for compatability reasons.

Actually it could be changed as existing code wouldn't break =/
But yeah, /* */ is the old style of commenting (// is C89 or C99?!) and should be used careful.

Oh, and thanks for repeating me guys

When commenting out parts of the code for testing, just do it like this:

When you want to include the code again, you just have to add a / at the beginning. Magic!

For comments, I use the // functions of my editor. I think it feels more distinguishable.

use
#ifdef somethingundefined
...
#endif

to comment any comments

Thats actually a very nifty trick!
Never though about that one, haha.
Speeds up toggeling commenting of blocks quite a bit.

Will use that in Java.