Piou-piou /
Ruined-World
| Conditions | 8 |
| Paths | 6 |
| Total Lines | 56 |
| Code Lines | 33 |
| Lines | 0 |
| Ratio | 0 % |
| Changes | 0 | ||
Small methods make your code easier to understand, in particular if combined with a good name. Besides, if your method is small, finding a good name is usually much easier.
For example, if you find yourself adding comments to a method's body, this is usually a good sign to extract the commented part to a new method, and use the comment as a starting point when coming up with a good name for this new method.
Commonly applied refactorings include:
If many parameters/temporary variables are present:
| 1 | <?php |
||
| 14 | public function __construct() { |
||
| 15 | $dbc1 = Bataille::getDb(); |
||
| 16 | |||
| 17 | $parametre = explode("-", self::$parametre_router); |
||
| 18 | Bataille::setValues(["batiments" => $parametre[0], "type_batiments" => $parametre[1]]); |
||
| 19 | |||
| 20 | //recuperation de tous les batiments du type |
||
| 21 | $query = $dbc1->select()->from($this->getTable($parametre[0]))->where("actif", "=", 1, "AND")->where("type", "=", $parametre[1])->get(); |
||
| 22 | |||
| 23 | if ((is_array($query)) && (count($query) > 0)) { |
||
| 24 | $batiments = []; |
||
| 25 | |||
| 26 | foreach ($query as $obj) { |
||
| 27 | $nom_batiment = $obj->nom; |
||
| 28 | $nom_batiment_sql = $obj->nom_table; |
||
| 29 | |||
| 30 | //on recupere les infos concernant le temps de construction et les batiment qu'il faudra pour construire |
||
| 31 | $query = $dbc1->select()->from($obj->nom_table)->where("ID_".$obj->nom_table, "=", 1)->get(); |
||
| 32 | |||
| 33 | if ((is_array($query)) && (count($query) == 1)) { |
||
| 34 | $pour_construire = []; |
||
| 35 | |||
| 36 | foreach ($query as $obj) { |
||
| 37 | $ressource_tmp = explode(", ", $obj->ressource_construire); |
||
| 38 | |||
| 39 | $ressource = [ |
||
| 40 | "fer" => $ressource_tmp[0], |
||
| 41 | "fuel" => $ressource_tmp[1], |
||
| 42 | "eau" => $ressource_tmp[2], |
||
| 43 | "electricite" => $ressource_tmp[3] |
||
| 44 | ]; |
||
| 45 | |||
| 46 | if ($obj->pour_construire != null) { |
||
| 47 | $pour_construire[] = unserialize($obj->pour_construire); |
||
| 48 | |||
| 49 | $pour_construire = $this->getPourConstruire($pour_construire); |
||
| 50 | } |
||
| 51 | else { |
||
| 52 | $pour_construire = []; |
||
| 53 | } |
||
| 54 | |||
| 55 | $batiments[] = [ |
||
| 56 | "nom_batiment" => $nom_batiment, |
||
| 57 | "nom_batiment_sql" => $nom_batiment_sql, |
||
| 58 | "niveau_batiment" => 1, |
||
| 59 | "temps_construction" => gmdate("H:i:s", $obj->temps_construction), |
||
| 60 | "ressource" => $ressource, |
||
| 61 | "pour_construire" => $pour_construire |
||
| 62 | ]; |
||
| 63 | } |
||
| 64 | } |
||
| 65 | } |
||
| 66 | |||
| 67 | Bataille::setValues(["liste_batiments" => $batiments]); |
||
| 68 | } |
||
| 69 | } |
||
| 70 | //-------------------------- END BUILDER ----------------------------------------------------------------------------// |
||
| 123 | } |
This check looks for unreachable code. It uses sophisticated control flow analysis techniques to find statements which will never be executed.
Unreachable code is most often the result of
return,dieorexitstatements that have been added for debug purposes.In the above example, the last
return falsewill never be executed, because a return statement has already been met in every possible execution path.