PHP: $_POST in switch statement a right way?

Question

I'm using switch statement on $_POST method and my script runs correctly but I think my code is not in a right way.

Here's my code:

<?php

switch(isset($_POST))
{
    case isset($_POST['A']):
      //do something
    break;
    case isset($_POST['B']):
      //do something
    break;
    case isset($_POST['C']):
      //do something
    break;
}

?>

my script runs correctly but I think my switch statement is not GOOD enough. Is there more simplier way or BETTER way using switch statement and $_POST method?

Answer 1

It's horrible but I prefer this than if-else-evil-chain:

switch(true)
{
    case isset($_POST['A']):
      //do something
    break;
    case isset($_POST['B']):
      //do something
    break;
    case isset($_POST['C']):
      //do something
    break;
}

Answer 2

check this out ;)

if (!empty($_POST)) {

         switch ($_POST) {
        case $_POST['A']:
            #do something;
            break;
        case $_POST['B']:
            #do something;
            break;
        case $_POST['C']:
            #do something;
            break;
    }
}

Answer 3

Maybe you mean something similar?

<?php

if(isset($_POST['A'])){
 // do something
}
if(isset($_POST['B'])){
 // do something
}
if(isset($_POST['C'])){
 // do something
}

?>

(This executes all the different matching branches instead of only the first one. Change the non-first if's to elseif if you want execute only the first matching branch.)

Answer 4

A nice way of putting a switch (){ case: } method is:

if (condition){
   // Do Something    
}elseif(condition){
   // Do Something
}elseif(condition){
   // Do Something    
}

This chain, is horrible to look at, but something I would suggest using in your unique case, alternativley you could go with @lame-up-ducks answer, but this is what i'd personally recommend using