Several methods or parameters?

Question

Ok, so I am developing a class here, and I have two options. I can either write several methods, or one method that takes on the value of Enum.

I am trying to find a better way to do this.

Let's take an example:

public class myClass
{ ...
    public void DoStuff1()
    { ... Do Stuff ... }

    public void DoStuff2()
    { ... Do Stuff ... }

    public void DoStuff3()
    { ... Do Stuff ... }
}

Well, everything makes sense, now an alternative way would be:

public class myClass
{ ...

    public Enum Option
    {
        Option1,
        Option2,
        Option3
    }

    public void DoStuff(Option option)
    { ... Do Stuff ... }
}

In terms of DRY, they are not so bad, because the code calls internal methods in many ways, so it selects only what is visible to the user.

So, what do you prefer, why, and are there any recommendations around this?

Answer 1

, ?

Answer 2

.

• /- DoStuff()
• , .

. / , Command Design Pattern, - .

Answer 3

, . , / , . , .

Answer 4

( ), - , . , . , , , - case , , .

, , GetData, , (.. ), .

Answer 5

. 1, 2 3 , ? , ? , ? Option1, Option2 Option3 .

... ? , ? ? , - .

, , . , - , , .

Answer 6

, DoStuff :

public void DoStuff(Option option)
{ 
  switch (option)
  {
     case Option1: /* Stuff 1 */ break;
     case Option2: /* Stuff 2 */ break;
     case Option3: /* Stuff 3 */ break;
  }
}

, , . : API ? , . , ( DoStuff1..DoStuff3 ) DoStuff,

public void DoStuff(Option option)
{ 
  switch (option)
  {
     case Option1: DoStuff1(); break;
     case Option2: DoStuff2(); break;
     case Option3: DoStuff3(); break;
  }
}

Answer 7

If the DoStuffX () methods have common functionality, I would use enums. If there is nothing in common, then I would use separate methods to avoid if-else / switch stmts.