supernova-ws /
SuperNova
| Conditions | 13 |
| Paths | 168 |
| Total Lines | 35 |
| Code Lines | 18 |
| 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 |
||
| 124 | function killer_add_planet($planet) { |
||
| 125 | global $final_cost; |
||
| 126 | |||
| 127 | $final_cost = array(); |
||
| 128 | $sn_group_resources_loot = sn_get_groups('resources_loot'); |
||
| 129 | /* |
||
| 130 | foreach($sn_group_resources_loot as &$value) |
||
| 131 | { |
||
| 132 | $value = get_unit_param($value, P_NAME); |
||
| 133 | } |
||
| 134 | */ |
||
| 135 | |||
| 136 | foreach (sn_get_groups('structures') as $unit_id) { |
||
| 137 | $build_level = mrc_get_level($user, $planet, $unit_id, true, true); |
||
| 138 | if ($build_level > 0) { |
||
| 139 | $unit_cost = get_unit_param($unit_id, 'cost'); |
||
| 140 | $build_factor = $unit_cost['factor'] != 1 ? (1 - pow($unit_cost['factor'], $build_level)) / (1 - $unit_cost['factor']) : $unit_cost['factor']; |
||
| 141 | foreach ($sn_group_resources_loot as $resource_id) { |
||
| 142 | $final_cost[$resource_id] += isset($unit_cost[$resource_id]) && $unit_cost[$resource_id] > 0 ? floor($unit_cost[$resource_id] * $build_factor) : 0; |
||
| 143 | } |
||
| 144 | } |
||
| 145 | } |
||
| 146 | |||
| 147 | foreach (sn_get_groups(array('defense', 'fleet')) as $unit_id) { |
||
| 148 | $unit_count = mrc_get_level($user, $planet, $unit_id, true, true); |
||
| 149 | if ($unit_count > 0) { |
||
| 150 | $unit_cost = get_unit_param($unit_id, 'cost'); |
||
| 151 | foreach ($sn_group_resources_loot as $resource_id) { |
||
| 152 | $final_cost[$resource_id] += isset($unit_cost[$resource_id]) && $unit_cost[$resource_id] > 0 ? floor($unit_cost[$resource_id] * $unit_count) : 0; |
||
| 153 | } |
||
| 154 | } |
||
| 155 | } |
||
| 156 | |||
| 157 | foreach ($sn_group_resources_loot as $resource_id) { |
||
| 158 | $final_cost[$resource_id] += floor(mrc_get_level($user, $planet, $resource_id, true, true)); |
||
| 159 | } |
||
| 161 |
Loading history...
The PSR-1: Basic Coding Standard recommends that a file should either introduce new symbols, that is classes, functions, constants or similar, or have side effects. Side effects are anything that executes logic, like for example printing output, changing ini settings or writing to a file.
The idea behind this recommendation is that merely auto-loading a class should not change the state of an application. It also promotes a cleaner style of programming and makes your code less prone to errors, because the logic is not spread out all over the place.
To learn more about the PSR-1, please see the PHP-FIG site on the PSR-1.