1.2 — Comments

A comment is a programmer-readable note that is inserted directly into the source code of the program. Comments are ignored by the compiler and are for the programmer’s use only.

In C++ there are two different styles of comments, both of which serve the same purpose: to help programmers document the code in some way.

Single-line comments

The // symbol begins a C++ single-line comment, which tells the compiler to ignore everything from the // symbol to the end of the line. For example:

Typically, the single-line comment is used to make a quick comment about a single line of code.

Having comments to the right of a line can make both the code and the comment hard to read, particularly if the line is long. If the lines are fairly short, the comments can simply be aligned (usually to a tab stop), like so:

However, if the lines are long, placing comments to the right can make your lines really long. In that case, single-line comments are often placed above the line it is commenting:

Author's note

The statements above represent one of our first encounters with snippets of code. Because snippets aren’t full programs, they aren’t able to be compiled by themselves. Rather, they exist to demonstrate specific concepts in a concise manner.

If you would like to compile a snippet, you’ll need to turn it into a full program in order for it to compile. Typically, that program will look something like this:

Multi-line comments

The /* and */ pair of symbols denotes a C-style multi-line comment. Everything in between the symbols is ignored.

Since everything between the symbols is ignored, you will sometimes see programmers “beautify” their multi-line comments:

Multi-line style comments can not be nested. Consequently, the following will have unexpected results:

When the compiler tries to compile this, it will ignore everything from the first /* to the first */. Since “this is not inside the comment */” is not considered part of the comment, the compiler will try to compile it. That will inevitably result in a compile error.

This is one place where using a syntax highlighter can be really useful, as the different coloring for comment should make clear what’s considered part of the comment vs not.


Don’t use multi-line comments inside other multi-line comments. Wrapping single-line comments inside a multi-line comment is okay.

Proper use of comments

Typically, comments should be used for three things. First, for a given library, program, or function, comments are best used to describe what the library, program, or function, does. These are typically placed at the top of the file or library, or immediately preceding the function. For example:

All of these comments give the reader a good idea of what the library, program, or function is trying to accomplish without having to look at the actual code. The user (possibly someone else, or you if you’re trying to reuse code you’ve previously written) can tell at a glance whether the code is relevant to what he or she is trying to accomplish. This is particularly important when working as part of a team, where not everybody will be familiar with all of the code.

Second, within a library, program, or function described above, comments can be used to describe how the code is going to accomplish its goal.

These comments give the user an idea of how the code is going to accomplish its goal without having to understand what each individual line of code does.

Third, at the statement level, comments should be used to describe why the code is doing something. A bad statement comment explains what the code is doing. If you ever write code that is so complex that needs a comment to explain what a statement is doing, you probably need to rewrite your statement, not comment it.

Here are some examples of bad line comments and good statement comments.

Bad comment:

Reason: We already can see that sight is being set to 0 by looking at the statement

Good comment:

Reason: Now we know why the player’s sight is being set to 0

Bad comment:

Reason: We can see that this is a cost calculation, but why is quantity multiplied by 2?

Good comment:

Reason: Now we know why this formula makes sense.

Programmers often have to make a tough decision between solving a problem one way, or solving it another way. Comments are a great way to remind yourself (or tell somebody else) the reason you made one decision instead of another.

Good comments:

Finally, comments should be written in a way that makes sense to someone who has no idea what the code does. It is often the case that a programmer will say “It’s obvious what this does! There’s no way I’ll forget about this”. Guess what? It’s not obvious, and you will be amazed how quickly you forget. :) You (or someone else) will thank you later for writing down the what, how, and why of your code in human language. Reading individual lines of code is easy. Understanding what goal they are meant to accomplish is not.

Best practice

Comment your code liberally, and write your comments as if speaking to someone who has no idea what the code does. Don’t assume you’ll remember why you made specific choices.

Author's note

Throughout the rest of this tutorial series, we’ll use comments inside code blocks to draw your attention to specific things, or help illustrate how things work (while ensuring the programs still compile). Astute readers will note that by the above standards, most of these comments are horrible. :) As you read through the rest of the tutorials, keep in mind that the comments are serving an intentional educational purpose, not trying to demonstrate what good comments look like.

Commenting out code

Converting one or more lines of code into a comment is called commenting out your code. This provides a convenient way to (temporarily) exclude parts of your code from being included in your compiled program.

To comment out a single line of code, simply use the // style comment to turn a line of code into a comment temporarily:

Uncommented out:

Commented out:

To comment out a block of code, use // on multiple lines of code, or the /* */ style comment to turn the block of code into a comment temporarily.

Uncommented out:

Commented out:


There are quite a few reasons you might want to do this:

1) You’re working on a new piece of code that won’t compile yet, and you need to run the program. The compiler won’t let you compile the code if there are compiler errors. Commenting out the code that won’t compile will allow the program to compile so you can run it. When you’re ready, you can uncomment the code, and continue working on it.

2) You’ve written new code that compiles but doesn’t work correctly, and you don’t have time to fix it until later. Commenting out the broken code will ensure the broken code doesn’t execute and cause problems until you can fix it.

3) To find the source of an error. If a program isn’t producing the desired results (or is crashing), it can sometimes be useful to disable parts of your code to see if you can isolate what’s causing it to not work correctly. If you comment out one or more lines of code, and your program starts working as expected (or stops crashing), odds are whatever you last commented out was part of the problem. You can then investigate why those lines of code are causing the problem.

4) You want to replace one piece of code with another piece of code. Instead of just deleting the original code, you can comment it out and leave it there for reference until you’re sure your new code works properly. Once you are sure your new code is working, you can remove the old commented out code. If you can’t get your new code to work, you can always delete the new code and uncomment the old code to revert to what you had before.

Commenting out code is a common thing to do while developing, so many IDEs provide support for commenting out a highlighted section of code. How you access this functionality varies by IDE.

For Visual Studio users

You can comment or uncomment a selection via Edit menu > Advanced > Comment Selection (or Uncomment Selection).

For Code::Blocks users

You can comment or uncomment a selection via Edit menu > Comment (or Uncomment, or Toggle comment, or any of the other comment tools).


If you always use single line comments for your normal comments, then you can always use multi-line comments to comment out your code without conflict. If you use multi-line comments to document your code, then commenting-out code using comments can become more challenging.

If you do need to comment out a code block that contains multi-line comments, you can also consider using the #if 0 preprocessor directive, which we discuss in lesson 2.9 -- Introduction to the preprocessor.


  • At the library, program, or function level, use comments to describe what.
  • Inside the library, program, or function, use comments to describe how.
  • At the statement level, use comments to describe why.

1.3 -- Introduction to objects and variables
1.1 -- Statements and the structure of a program

159 comments to 1.2 — Comments

  • Aiden

    i tried to do

    it worked, but it didnt do anything? im wondering if its supposed to and im doing something wrong

    • Alex

      You mean it compiled but didn't produce any output? Did you actually run the program you created? If so, it's possible the output flashed on the screen and then disappeared when the program terminated. Lesson 0.7 contains some advice on how to address that issue.

  • Gabor

    Hi Alex!

    At the part "Multi-line style comments do not nest." Would not be it better to write

    (Comment ends at the /, not at the preceding *.)
    Thanks for the tutorial!

  • Mato

    Hi Alex,
    Please could you tell about:
    //(* *)// and
    kind of comments.
    Thank you,

    • Alex

      //(* *)// is just a // style comment with other symbols added in for fanciness.
      \ is not a comment at all. I don't know what this is meant to be.

  • dartagnan

    thanks for all the hard work,really appreciate it

  • Mohammad Abolnejadian

    in xcode it says to make endl; to std::endl

  • Raman Kamat

    FABULOUS WORK :-) :-)

  • Warlaan

    Overall a great tutorial, but as a senior programmer I disagree with the first example for a bad comment.

    Imho that's a good comment, because comments aren't as much about explaining the code or providing orientation as they are about explaining your intention. If you look at this code for example:

    It's still very obvious what the code does - unfortunately it's also not what was intended. With both the code and the comment easy to read it is now very easy to spot the bug.

    A comment like

    describes a higher level of code, e.g.:

  • Niranjan.A.S

    Great tutorial

  • Olaf

    This is beyond power ><

  • Kees van de Wetering

    This is great stuff, thanks.

  • subhranshu

    thanks a lot
    very well structured tutorial

  • Jeremy

    Microsoft recommends using the preprocessor to comment out code, since block comments cannot be nested (assuming there are already block comments in the code you're trying to comment out).

    // 0 is always 'false' so the code between #if 0 and #endif will not be compiled:
    #if 0

    ** Assume this is a bunch of code
    ** that you wish to comment out.


    • Alex

      That will work, but the downside is that your IDE won't color code it as a comment for you. That can lead to errors, as it makes it much harder to tell what code is "live" vs not.

      Personally, I like to use // for normal comments, and /* */ for commented out code. I just have to make sure I don't comment out the same block of code more than once.

      Fortunately, if you do try to nest C-style comments, it usually causes compiler errors because the compiler doesn't know what to do with your uncommented comment text.

  • Dr.Chase

    This is really helpful stuff.
    I prefer learning this over the bjarne stroustrop book. He is like "Oh look I invented this it's so cool BTW I won't explain stuff well coz I'm too awesome for that". Jokin' :D.
    But this site makes things more comprehensable. Big LIKE!
    I'm a University student and I learn programming. The teacher actually doesn't teach anything.

  • LIkith C

    My Comment

    Fantastic tutorial!!!

  • Maria

    Hey! I don't understand the commenting out the code???

    • Peverell

      This is your HelloWorld code:

      This is what he means by commenting out the code. I have commented out line 7:

      That is, if you don't immediately want a statement to be executed for whatever reason, adding // at the beginning of it i.e. commenting it out will enable your compiler to ignore it.

  • Jim

    I would like to comment on the comment section... it was very good. I cannot comment on the comments of the commentators that posted comments for that would make this comment too long.

    • Alex

      We have enabled nested comments, so you can comment on the comments of the commentators that posted comments, should you wish. :)

      • Darren

        Just checking it was true that I could comment on the comment about being able to comment on the comments of the commentators that posted comments about commenting. I have too much time on my hands :(

  • Sajid Ali Badsha Gilgiti

    :) programing is fun.... programing in c++ is really fun :)

  • Sergey

    Strange thing is that obvious rule to comment your code still needs a long discussion. "Bad comments" worse than "good comments". But "no comments" is worst.

  • emerald820

    importance and correct usage of comments has been explained in an excellent way..thanks

  • Helleri

    Ok. wait...I don't get how I am supposed to use comments to not explain what something does but also make it clear what something does. I feel like I was told to do one thing and then told to do the opposite.

  • hawk1821

    excellent reading for beginners

  • A bad statement comment explains what the code is doing, you claim.

    That is true in many cases, but sometimes it can be very helpful to explain what code is doing.

    For example, when I learned PHP I had a hard time remembering the meaning of % (modulus) and added the explanation remainder of division every time I used modulus for a while until I know the explanation by heart.

    I think the best approach is to simply add all comments you find helpful.

  • Nice explanation about comments on comments

  • ImGoingToBePro

  • seb

    what do u mean by commenting out a code

    • drake

      what he means is that you add the "//" to the beginning of a line of code in order to turn it into a comment. This causes the compiler to ignore that line of code.

  • wastefuldragon

  • Julian

    I think of comments as a kind of "language translation" method. Imagine you are trying to learn another language such as French. As you are learning French, you are obviously not going to remember everything you learn after one look; there will be words that you will forget the meaning of etc unless of course you go over them many many times. Now imagine you're only part way through learning French but you go to France for a holiday, forcing you to speak French in most places you visit. The ideal solution would be to take a French-English dictionary with you wherever you go. You can't speak French fluently so you must use the French-English dictionary to help you understand different sentences in French. This is like using a C++-English dictionary to help you remember what sentences in C++ mean. Obviously, it would be very hard to eventually be able to speak C++ fluently, so the comments are kind of like C++ to English translations.

  • Very nice. Comments are always good to learn.

Leave a Comment

Put all code inside code tags: [code]your code here[/code]