| 9 | | == Example in D == |
|---|
| | 9 | |
|---|
| | 10 | == How is `switch-case` useful? == |
|---|
| | 11 | |
|---|
| | 12 | Let's say you write a program that has a menu with a bunch of mutually exclusive options. |
|---|
| | 13 | |
|---|
| | 14 | {{{ |
|---|
| | 15 | +---------+------+-------+------+ |
|---|
| | 16 | | File | Edit | Tools | Help | |
|---|
| | 17 | +---------+------+-------+------+ |
|---|
| | 18 | | New | |
|---|
| | 19 | | Open | |
|---|
| | 20 | | Save | |
|---|
| | 21 | | Print | |
|---|
| | 22 | |---------+ |
|---|
| | 23 | | Exit | |
|---|
| | 24 | +---------+ |
|---|
| | 25 | }}} |
|---|
| | 26 | |
|---|
| | 27 | This is just the kind of situation that lead to the creation of the switch-case construct: only one of these options can be clicked at any given time. You can't click "Open" and "Exit" at the same time. So let's just go down the list. Maybe "New" was clicked, so run subroutine `NewWasClicked()`. If "Open" was clicked, then run subroutine `OpenWasClicked()`. And so on down list. If "Exit" was clicked then just `PostQuitMessage(0)`. Finally the `default case` is there so that you can catch whatever might fall through the cracks. |
|---|
| | 28 | |
|---|
| | 29 | == Don't fall through (unless you want to) == |
|---|
| | 30 | |
|---|
| | 31 | D follows in the C/C++ tradition of "falling through" from the matched case to the cases below if there isn't a `break` statement. So unless you actually want all the code for the lower cases executed when the upper case is found, don't forget to include those `break`s. |
|---|
| | 32 | |
|---|
| | 33 | |
|---|
| | 34 | == Example in the D Programming Language == |
|---|
