Adding values returned by different cases in switch

[rocksters]

HI , Can u tell how to add the two values returned by two different fuctions in different cases of switches????

[Meetee]

HI , Can u tell how to add the two values returned by two different fuctions in different cases of switches????

What have you done so far? I can help you only if you have tried something on this issue. Also clearify about different cases of switches. I don't understand, you want switch case in individual functions or function that calculates addition.

Regards.

PS. Refer posting guidelines before posting. It is very helpful.

[sicarie]

HI , Can u tell how to add the two values returned by two different fuctions in different cases of switches????

No. A switch statement is based on cases, where one case will execute and the others won't (if it's designed properly). However, if you did set it up so that your cases ran together (very, very bad form), you said the variables were returned.

So store them and add them.

[weaknessforcats]

if you did set it up so that your cases ran together (very, very bad form),

Not necessarily. I may happen that multiple cases have the same code. Like January, March, May, July, August,October and December all have 31 days:

switch (month)
{
   case January:
   case March:
   case May:
   case July:
   case August:
   case October:
   case December:
           DaysInMonth = 31;
           break;
etc...
 

[sicarie]

Not necessarily. I may happen that multiple cases have the same code. Like January, March, May, July, August,October and December all have 31 days:

switch (month)
{
   case January:
   case March:
   case May:
   case July:
   case August:
   case October:
   case December:
           DaysInMonth = 31;
           break;
etc...
 

I see your point, weaknessforcats, but I would still think that such 'cascading' cases could probably be better dealt with in another fashion (such as in the specific example above, using a date class that can have some sort of 'getDaysInMonth()' method). Especially for writing easily-maintainable code that you can go back and make changes on without causing unintended effects, I would avoid them. I suppose that is more personal style, though.