Should we break the default case in switch statement?

Question

Assuming this example code (source):

#include 

void playgame()
{
    printf( \"Play game called\" );
}
void loadgame()
{
    printf( \"Load g         


        

Answer 1

For one thing, you should think about why we should use break in switch statement. Look at this no-breaking switch statement.

switch ( input ) {
    case 1:            /* Note the colon, not a semicolon */
        playgame();
    case 2:
        loadgame();
    case 3:
        playmultiplayer();
    case 4:
        printf( "Thanks for playing!\n" );
    default:
        printf( "Bad input, quitting!\n" );
}

Suppose input == 1. The program will call playgame() of course, but since there's no break, program won't finish the switch but call loadgame(), playmultiplayer(), two printfs sequentially.

To avoid this, we use break.

case 1:
    playgame();
    break; /* here */
case 2:
    ...

Because of break, the program finishes switch statement before running codes of case 2. That's our expected result, isn't it?

Your switch is this:

switch ( input ) {
    case 1:            /* Note the colon, not a semicolon */
        playgame();
        break;
    case 2:
        loadgame();
        break;
    case 3:
        playmultiplayer();
        break;
    case 4:
        printf( "Thanks for playing!\n" );
        break;
    default:
        printf( "Bad input, quitting!\n" );
        break;
}

Since there's no cases after default, there's no effect whether you write break on default or not. However, you can easily suppose to write a new case.

    default:
        printf( "Thanks for playing!\n" );
        /* what happens if there's no `break`...? */
    case 5:
        the_new_feature();
        break;
}

It's common-mistakes in C/C++. If you add new feature after 5 years and you completely forget it, it'll become a very buggy bug. Some modern language (e.g. C#, ...) even forbid switch-case without break or return.

Conclusion: There's no problem in syntax, but it's very bad practice and using break is highly recommended.

Answer 2

There is no difference if you omit or if you leave the break statement. It is a matter of taste.

However, it is good practice to write the break statement for different reasons.

Take a look at programmers exchange.

Answer 3

Break Seems to Be Optional

break seems to be optional in that case. and also your code will work almost fine.

However

in many situations adding break improves your code and protect your code from errors/exceptions.

it increases readability, consistency and more error free.

some language like C# break(or other control-flow statement that exits the case) is technically needed after the last alternative. dan04

so for better programming practices i suggest one should use it.

see this excellent post for more details.

Answer 4

Should we use a break; in the last default case?

From The C programming language - Second edition (K&R 2):

Chapter 3.4 Switch

As a matter of good form, put a break after the last case (the default here) even though it's logically unnecessary. Some day when another case gets added at the end, this bit of defensive programming will save you.

Answer 5

if default case is at last then break statement have no use. if it is before any other case then break is required. since usually we are putting default at the end so you can omit it..

Answer 6

Actually, you don't need the break in default case. And as your checking, it's the same if you don't have break in default case.

But in my opinion, you should have the break in default case, because:

1. It make your code is have a form in every case.
2. It's good with current compiler but maybe not with specific other compiler. So you should make it good well to prevent issue from future.