13.2. switch statement

It’s hard to mention enumerated types without mentioning switch statements, because they often go hand in hand. A switch statement is an alternative to a chained conditional that is syntactically prettier and often more efficient. It looks like this:

switch (symbol) {
case '+':
  perform_addition ();
  break;
case '*':
  perform_multiplication ();
  break;
default:
  cout << "I only know how to perform addition and multiplication" << endl;
  break;
}

This switch statement is equivalent to the following chained conditional:

if (symbol == '+') {
  perform_addition ();
}
else if (symbol == '*') {
  perform_multiplication ();
}
else {
  cout << "I only know how to perform addition and multiplication" << endl;
}

The break statements are necessary in each branch in a switch statement because otherwise the flow of execution “falls through” to the next case.

Note

Be sure to incorporate a break statment into each branch so that the flow of execution stops after that branch.

Without the break statements, the symbol + would make the program perform addition, and then perform multiplication, and then print the error message. Occasionally this feature is useful, but most of the time it is a source of errors when people forget the break statements.

Take a look at the active code below that allows you to choose your starter Pokemon. If you change the value of type, it will change the Pokemon you choose. Notice how if you don’t assign type to a valid type, it outputs the default message. Try taking out the break statements in each case. What happens if you run the code with type as ‘g’ afterwards?

switch statements work with integers, characters, and enumerated types. For example, to convert a Suit to the corresponding string, we could use something like:

switch (suit) {
case CLUBS:     return "Clubs";
case DIAMONDS:  return "Diamonds";
case HEARTS:    return "Hearts";
case SPADES:    return "Spades";
default:        return "Not a valid suit";
}

In this case we don’t need break statements because the return statements cause the flow of execution to return to the caller instead of falling through to the next case.

In general it is good style to include a default case in every switch statement, to handle errors or unexpected values.

Before you keep reading...

Making great stuff takes time and $$. If you appreciate the book you are reading now and want to keep quality materials free for other students please consider a donation to Runestone Academy. We ask that you consider a $10 donation, but if you can give more thats great, if $10 is too much for your budget we would be happy with whatever you can afford as a show of support.

You have attempted 1 of 7 activities on this page