How to avoid writing a switch too long?

Question

There is a lot of code in my current project using switch with too many cases.

Switch(c)
{
case CASENUMBERONE:
//50-100 lines of code in each code
...
case CASENUMBERTWENTY:
..
}


//thousands of lines of macro definition in another file
#define CASENUMBERONE 1
...
#define CASENUMBERTWENTY 20
...

This does not seem to be a reasonable programming style. How to avoid this?

Answer 1

It depends.

• You can write a function for each case. You can embed them if you are concerned about performance, but in real life, in fact, you can get a performance boost due to the presence of separate functions due to better consistency of the command cache.

• , . , /, . - , - . , NULL.

• .

Answer 2

@Zain, / ( , ).

, , , .

handler[c](): -)

, , .

, ( switch).

hth.,

Answer 3

, . , , , , . "" , . , , , , . .

, .

Answer 4

1500 = (50-100 ) * 20

. .

/ .

/, , . ( )

( )

Answer 5

, .

Answer 6

, . , , , ; , , .

, - , , ; .

++ :/

Answer 7

, , ,

Answer 8

, . boost:: assign:: map_list_of.

find . , .

Answer 9

- :

, case foo , . , , . , , .

, , ptr- > foo (c) ptr- > foo(). , .