Structures de Contrôles
Les structures de contrôles incluent les 'if', 'for', 'while',
'switch', etc. Vous trouverez ici un exemple de structure 'if' qui est la
plus compliquée :
<?php
if ((condition1) || (condition2)) {
action1;
} elseif ((condition3) && (condition4)) {
action2;
} else {
defaultaction;
}
?>
Les instructions de contrôle doivent avoir un espace entre le mot
clé de l'instruction et la parenthèse ouvrante,
afin de les distinguer des appels de fonctions.
Il est vivement recommandé de toujours utiliser des accolades,
même dans les situations où elles sont techniquement
optionnelles.
Leur présence augmente la lisibilité du code
et réduit le risque d'erreur logique lors de l'ajout de nouvelles
lignes de code.
Pour l'instruction 'switch' :
<?php
switch (condition) {
case 1:
action1;
break;
case 2:
action2;
break;
default:
le job par defaut;
break;
}
?>
 Indentation et longueur de lignes (Previous)
|
(Next) Appels de Fonctions
|
|
|
Download Documentation
|
Last updated: Sun, 18 Oct 2009 |
|
Do you think that something on this page is wrong? Please file a bug report or add a note.
|
| User Notes: |
Note by: bobvandell@hotmail.com
I'm with Maga on this one. That's how I've been doing it for years.
Indent from the case so that the case it's self stands out.
My strong belief is still that this would add a nice way to represent loops...
switch (condition)
{
case 1;
action 1;
break1;
case 2;
action 2;
break2;
}
This makes the system much more readable and easy to understand. Every indent specifies a child. and two indents is especially useful when you are reading about 100 lines of code. It truely helps!
Note by: Maga
I think that better is:
<?php
switch (condition)
{
case 1:
action1;
break;
case 2:
action2;
break;
default:
defaultaction;
break;
}
Indentation+Brakes
?>
Phil, the indentation like in your example (i.e. with 4 spaces for the "case" statements) is also accepted in the PEAR coding standards.
Note by: phil@signalz.com
I would have expected more indentation, like this
<?php
switch (condition) {
case 1:
action1;
break;
case 2:
action2;
break;
default:
defaultaction;
break;
}
?>
Note by: dpn12@comcast.net
Might you consider adding to your current K&R format, below
...
switch (condition) {
case 1:
action1;
break;
case 2:
action2;
break;
}
...
/**/
...
switch (condition)
{
case 1:
action1;
break;
case 2:
action2;
break;
}
...
this above format that some believe to be more readable?
|
|
