5.3 — Switch statements

Although it is possible to chain many if-else statements together, this is difficult to read. Consider the following program:

Because doing if-else chains on a single variable testing for equality is so common, C++ provides an alternative conditional branching operator called a switch. Here is the same program as above in switch form:

The overall idea behind switch statements is simple: the switch expression is evaluated to produce a value, and each case label is tested against this value for equality. If a case label matches, the statements after the case label are executed. If no case label matches the switch expression, the statements after the default label are executed (if it exists).

Because of the way they are implemented, switch statements are typically more efficient than if-else chains.

Let’s examine each of these concepts in more detail.

Starting a switch

We start a switch statement by using the switch keyword, followed by the expression that we would like to evaluate. Typically this expression is just a single variable, but it can be something more complex like nX + 2 or nX - nY. The one restriction on this expression is that it must evaluate to an integral type (that is, char, short, int, long, long long, or enum). Floating point variables and other non-integral types may not be used here.

Following the switch expression, we declare a block. Inside the block, we use labels to define all of the values we want to test for equality. There are two kinds of labels.

Case labels

The first kind of label is the case label, which is declared using the case keyword and followed by a constant expression. A constant expression is one that evaluates to a constant value -- in other words, either a literal (such as 5), an enum (such as COLOR_RED), or a constant variable (such as x, when x has been defined as a const int).

The constant expression following the case label is tested for equality against the expression following the switch keyword. If they match, the code under the case label is executed.

It is worth noting that all case label expressions must evaluate to a unique value. That is, you can not do this:

It is possible to have multiple case labels refer to the same statements. The following function uses multiple cases to test if the ‘c’ parameter is an ASCII digit.

In the case where c is an ASCII digit, the first statement after the matching case statement is executed, which is “return true”.

The default label

The second kind of label is the default label (often called the “default case”), which is declared using the default keyword. The code under this label gets executed if none of the cases match the switch expression. The default label is optional, and there can only be one default label per switch statement. It is also typically declared as the last label in the switch block, though this is not strictly necessary.

In the isDigit() example above, if c is not an ASCII digit, the default case executes and returns false.

Switch execution and fall-through

One of the trickiest things about case statements is the way in which execution proceeds when a case is matched. When a case is matched (or the default is executed), execution begins at the first statement following that label and continues until one of the following termination conditions is true:
1) The end of the switch block is reached
2) A return statement occurs
3) A goto statement occurs
4) A break statement occurs
5) Something else interrupts the normal flow of the program (e.g. a call to exit(), an exception occurs, the universe implodes, etc…)

Note that if none of these termination conditions are met, cases will overflow into subsequent cases! Consider the following snippet:

This snippet prints the result:


This is probably not what we wanted! When execution flows from one case into another case, this is called fall-through. Fall-through is almost never desired by the programmer, so in the rare case where it is, it is common practice to leave a comment stating that the fall-through is intentional.

Break statements

A break statement (declared using the break keyword) tells the compiler that we are done with this switch (or while, do while, or for loop). After a break statement is encountered, execution continues with the statement after the end of the switch block.

Let’s look at our last example with break statements properly inserted:

Now, when case 2 matches, the integer 2 will be output, and the break statement will cause the switch to terminate. The other cases are skipped.

Warning: Forgetting the break statement at the end of the case statements is one of the most common C++ mistakes made!

Multiple statements inside a switch block

With if statements, you can only have a single statement after the if-condition, and that statement is considered to be implicitly inside a block:

However, with switch statements, you are allowed to have multiple statements after a case label, and they are not considered to be inside an implicit block.

In the above example, the 4 statements between the case label and default label are part of case 1, but not considered to be inside an implicit block.

If this seems a bit inconsistent, it is.

Variable declaration and initialization inside case statements

You can declare (but not initialize) variables inside the switch, both before and after the case labels:

Note that although variable y was defined in case 1, it was used in case 2 as well. Because the statements under each case are not inside an implicit block, that means all statements inside the switch are part of the same scope. Thus, a variable defined in one case can be used in another case, even if the case in which the variable is defined is never executed!

This may seem a bit counter-intuitive, so let’s examine why. When you define a local variable like “int y;”, the variable isn’t created at that point -- it’s actually created at the start of the block it’s declared in. However, it is not visible (in scope) until the point of declaration. The declaration statement doesn’t need to execute -- it just tells the compiler that the variable can be used past that point. So with that in mind, it’s a little less weird that a variable declared in one case statement can be used in another cases statement, even if the case statement that declares the variable is never executed.

However, initialization of variables directly underneath a case label is disallowed and will cause a compile error. This is because initializing a variable does require execution, and the case statement containing the initialization may not be executed!

If a case needs to define and/or initialize a new variable, best practice is to do so inside a block underneath the case statement:

Rule: If defining variables used in a case statement, do so in a block inside the case (or before the switch if appropriate)


1) Write a function called calculate() that takes two integers and a char representing one of the following mathematical operations: +, -, *, /, or % (modulus). Use a switch statement to perform the appropriate mathematical operation on the integers, and return the result. If an invalid operator is passed into the function, the function should print an error. For the division operator, do an integer division.

2) Define an enum (or enum class, if using a C++11 capable compiler) named Animal that contains the following animals: pig, chicken, goat, cat, dog, ostrich. Write a function named getAnimalName() that takes an Animal parameter and uses a switch statement to return the name for that animal as a std::string. Write another function named printNumberOfLegs() that uses a switch statement to print the number of legs each animal walks on. Make sure both functions have a default case that prints an error message. Call printNumberOfLegs() from main() with a cat and a chicken. Your output should look like this:

A cat has 4 legs.
A chicken has 2 legs.

Quiz answers

1) Show Solution

2) Show Solution

5.4 -- Goto statements
5.2 -- If statements

235 comments to 5.3 — Switch statements

  • Jack

    If you are returning a value inside a case label, is there any need to break as there is no chance of fall-through? I know the break won't be executed, but is it good practice to keep it there? ie:

    Poor example, but just to illustrate the point. Some languages complain about an unreachable statement (I've seen this error in Java a few times when you return and then write more statements under it), is this true for some versions of C++?

    • nascardriver

      Hi Jack!

      The break after a return will never be reached and adding a break won't change anything.
      I still like having the break there just for good measures.

  • Henry

    Hi Alex

    Your solution is good but it has a bug
    To reproduce, try to use an animal that is not defined and the error message will come out all weird.
    e.g: printNumberOfLegs(Animal::TIGER);

    I think my solution you should not break the cout message
    So do something like that:
    void printNumberOfLegs(Animal a) {
      using namespace std;

      switch (a) {
        case Animal::CHICKEN:
        case Animal::OSTRICH:
          cout << "A " << getAnimalName(a) << " has 2 legs.\n";
        case Animal::GOAT:
        case Animal::CAT:
        case Animal::DOG:
        case Animal::PIG:
          cout << "A " << getAnimalName(a) << " has 4 legs.\n"; break;
        default : cout << "ERROR: undefined animal!\n";

    You can break the last part of the message but then you need to use return and not break.

    • Alex

      Example updated to use "???" as the number of legs instead of the more descriptive error message. Either way is fine, as this message should only come up as a defect.

  • ArmaIG

    Hi Teachers, when I enter anything else that isn't a number when the program is asking for an integer, the programs executes the rest incorrectly, is there anyway to deal with that problem with the tools we know so far?

    • nascardriver

      Hi ArmaIG!

      This is covered in lesson 5.10.
      Now that you know of switch-statements, those are even better than an if-else-if in your monster to string function.

      * Lesson 5.10 - std::cin, extraction, and dealing with invalid text input

  • Dayyan218

    I wanted to ask, when is it a good time to use switch statements instead of if statements?
    To me switch statements aren't as easy to read as if-else statements. What are the pros of using switch statements over if-else statements?

    • nascardriver

      Hi Dayyan!

      "Use 'switch' when you have a limited set of values that you want to test against, eg. enums or characters.
      Use 'if' otherwise."

      > What are the pros of using switch statements over if-else statements?
      It's easier for your compiler to optimize switch-statements than if-else-statements.

  • Rohit

    You mention that variables can't be initialized inside a case "because initializing a variable does require execution, and the case statement containing the initialization may not be executed!"

    So I'm curious as to why it's illegal to initialize before all of the case labels? Because all the statements before the first case are executed anyway right?

    This gives the error code C2360 "initialization of 'x' is skipped by 'case' label" in VS 2017. I'm wondering what's going on.
    I tried to put 'x' in its own block and declare it as a static int to try to access it outside of the block scope but that doesn't work. I had forgotten that static variables are only accessible in the block they're declared. Regardless, the initial issue of it not letting me initialize there still occurred. (edit: scratch that, it let me initialize in its own block. but if i can't access it after the block then it's useless anyway.)

    I can always declare on one line and assign on the next but I was just curious as to why this happens.

  • Samira Ferdi

    Hi nascardriver! Thank you for reply!
    So, when the best practice to use switch-case rather than if-else and otherwise?

    • nascardriver

      Hi Samira!

      Use 'switch' when you have a limited set of values that you want to test against, eg. enums or characters.
      Use 'if' otherwise.
      That's how I do it.

  • Samira Ferdi

    So, the only difference betwen if-else chain and switch-case is the switch-case is more easier to read than if-else chain?
    When best practice to use if-else rather than switch-case and otherwise?

    • nascardriver

      Hi Samira!

      No, there are more differences.

      * You can only switch one value whereas if-elseif takes any boolean expression.
      * "cases will overflow into subsequent cases", 'if' doesn't.
      * 'switch' behaves differently when using blocks vs when not using blocks: "You can declare (but not initialize) variables inside the switch", 'if' can initialize.

Leave a Comment

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