How to explain why a developer should avoid case statements and create new classes?

Question

I have several times to try to explain to the developer why they should change a class that has multiple instances

switch(m_type) {
  case TYPE_A:
    ...
    break;

  case TYPE_A:
    ...
    break

  ...
}

Where m_type is a (final) reference to an enum specifying the type of instance.

Whenever I see this, I think it's time to split the class into several subclasses, where the particular class you create determines the type. The argument I always return is this: "It seems you should not create all these classes with hardly any code, what will they do there? Like 2 methods or something!"

, , , . , , .., . , , . , , , , , , , .

, , , - , ?

,

Answer 1

: : . .

- :

Replace Type Code , . , , . . , .

, .

Answer 2

, case, . . C- , Java, . () () .

, , , # 2 , , , , .

, . switch . , , , . , , .

Answer 3

, . , "" , , , .

Answer 4

Single-Choice , , . . , switch, , . , , , .

Answer 5

, , switch.

Answer 6

, . vtable ( ++) , , , .

Answer 7

, - . , case, , , , .

.

Answer 8

The code you specify directly violates the Open / Closed Principle (“O” in SOLID). As for OOP, this should be enough to do your thing .; -)