Thread: Switch/case vs if/else

There are 2 sets of key words that can potentially do the same thing - switch/case and if/else. Question is, which is the better method to use for something like this?

Code:

unsigned int CaseID;

...

// compare this
switch(CaseID)
{
   case 1:
      // do stuff if the "CaseID" variable is 1
      break;
   case 2:
      // do stuff if the "CaseID" variable is 2
      break;
   default:
      // do stuff if the "CaseID" variable is anything else
}

// to this
if (CaseID == 1)
{
   // do stuff if the "CaseID" variable is 1
}

else if (CaseID == 2)
{
   // do stuff if the "CaseID" variable is 2
}

else
{
   // do stuff if the "CaseID" variable is anything else
}

Both methods accomplish exactly the same effect so what is the difference? Performance (aka faster to process)? Readability? Something else?

there is much debate and has been much discussion about if else versus switch, none of it conclusive. in my opinion a switch is nearly always preferable once you get to 4 or even 3 if else statements and beyond, its just much clearer, even though if else is quite easy to read, a switch to me is just a nicer structure to look at.
If your cases are all nicely consecutive then a switch (I read) will more than likely be consolidated to a jump table at compile time. I also read You cannot include conditional test as case labels for this reason.

What's a jump table?

I usually prefer if/else over switch/case because, to me, if/else reads better as it reads more like plain English. "If ID number equals exactly 1, test equals 1" is much easier to read due to better English correctness than "case ID number 1, test equals 1". Of course, that's just my opinion. Whether 50 items are listed or just 2, I otherwise have a strong preference toward using if/else and, recalling switch/case, I was wondering if I should be using switch/case instead of if else for series like explained in my initial post, especially for the menus where it wouldn't be unusual to see numerous options listed, some with submenus (which means nested switch/case), others with nothing more than a function call and they're generally sequential.

Originally Posted by ulillillia

What's a jump table?

It might be a good idea to search the Web concerning this.

Originally Posted by ulillillia

I usually prefer if/else over switch/case because, to me, if/else reads better as it reads more like plain English.

You have a point there, but then the condition of an if statement can be just about any boolean expression, whereas a switch is more specific, i.e., some integral value is being compared with a series of integral values. I think that this can actually make one's intention more explicit, as in your example of menu options.

as in your example of menu options.

Exactly, it just provides that little layer of abstraction to visualise whats is happening and intended,

some integral value is being compared with a series of integral values

This again supports comprehension, if you read a line that says switch(verticies) and you know you are working on a fractal program then that places the following cases perfectly into context, and your mind naturally sees it, if you are following a stack of logic statements, albeit on the same theme, and even if they are clear, then reading down a tree going 'if this is not that, then, unless if this is not that, then, unless...sure its english but i think its translation into the switch is more succinct and elegant.

I fail to see how if/else is more compact.

Knowing that a compiler may use a jump table or even a binary search for a switch statement isn't necessary.

It is enough to simply realise that with an if/else-if chain, you're telling the compiler exactly in which order to check these things, and it must do as you asked. There is very little room for the compiler to work its own optimisation magic.
With a swtich however, the compiler is free to make sure that it arrives at the correct case by any means necessary. It can do tests in any order it likes, or compute any kind of jump table it likes, or use profile guided optimisation to put the more common cases first, as long as it gives the right end result. So there is far more room for compiler optimisation to kick in.

It's about telling the compiler what you want, any letting it work out the how, rather than telling it the how directly.

Code:

    switch (y)
    {
        case 8: printf("Correct.\n"); break;
        default: printf("Incorrect.\n"); break;
    }

2 vs 5 lines. Add more than one statement per if and the difference is negligible.

Originally Posted by Elysia

Code:

    switch (y)
    {
        case 8: printf("Correct.\n"); break;
        default: printf("Incorrect.\n"); break;
    }

2 vs 5 lines. Add more than one statement per if and the difference is negligible.

You can put as many statements as you want on one line.

Code:

if (!argv[1]) printf("There are no arguments.\n"); return 1;
else printf("There is at least one argument.\n"); return 0;

EDIT: Ah, you got me there. I still prefer if/else.

You cannot, because that's a compile error.