The variable symbol '$' should be considered as the highest-precedence operator, so that the variable variables such as $$a[0] won't confuse the parser. [http://www.php.net/manual/en/language.variables.variable.php]
Operadores
Índice
- Operadores Aritméticos
- Operadores de Atribuição
- Operador Bit-a-bit
- Operadores de Comparação
- Operadores de controle de erro
- Operadores de Execução
- Operadores de Incremento/Decremento
- Operadores Lógicos
- Operadores de String
- Operadores de Arrays
- Operadores de tipo
Um operador é algo que você alimenta com um ou mais valores (ou expressões, no jargão de programação) e que devolve outro valor (e por isso os próprios construtores se tormam expressões). Assim, você pode pensar que as funções e os construtores que retornam valores (como o print) são operadores e os outros que não retornam nada (como echo) como uma outra coisa.
Há três tipos de operadores. Primeiramente, os operadores unários, que operam em apenas um valor. Por exemplo, ! (operador de negação) ou o ++ (operador de incremento). No segundo grupo estão os operadores binários, o o grupo que contém a maioria dos operadores que o PHP suporta, com uma lista completa logo abaixo na seção Precedência de operadores.
O terceiro grupo é do operador ternário: ?:. Ele pode ser usado para selecionar entre dois valores dependendo de uma terceira, em vez de selecionar duas sentenças ou encadeamentos de execução. Englobar expressões ternárias com parênteses é uma boa idéia.
Precedência de Operadores
A precedência de um operador especifica quem tem mais prioridade quando há duas delas juntas. Por exemplo, na expressão, 1 + 5 * 3, a resposta é 16 e não 18 porque o operador de multiplicação ("*") tem prioridade de precedência que o operador de adição ("+"). Parênteses podem ser utilizados para forçar a precedência, se necessário. Assim, (1 + 5) * 3 é avaliado como 18. Se a precedência do operador é igual, a associatividade da esquerda para direita é usada.
A tabela seguinte mostra a precedência dos operadores, da maior precedência no começo. Operadores com a mesma precedência estão na mesma linha, no caso a associatividade deles decidide qual ordem eles são avaliados.
| Associação | Operador | Informação adicional |
|---|---|---|
| não associativo | clone new | clone e new |
| esquerda | [ | array() |
| não associativo | ++ -- | incremento/decremento |
| não associativo | ~ - (int) (float) (string) (array) (object) (bool) @ | tipos |
| não associativo | instanceof | tipos |
| direita | ! | lógico |
| esquerda | * / % | aritmético |
| esquerda | + - . | aritmético e string |
| esquerda | << >> | Bit-a-bit |
| não associativo | < <= > >= <> | comparação |
| não associativo | == != === !== | comparação |
| esquerda | & | Bit-a-bit e referências |
| esquerda | ^ | Bit-a-bit |
| esquerda | | | Bit-a-bit |
| esquerda | && | lógico |
| esquerda | || | lógico |
| esquerda | ? : | ternário |
| direita | = += -= *= /= .= %= &= |= ^= <<= >>= | atribuição |
| esquerda | and | lógico |
| esquerda | xor | lógico |
| esquerda | or | lógico |
| esquerda | , | muitos usos |
Associatividade a esquerda significa que a expressão é avaliada da esquerda para direita, associatividade a direita o oposto.
Exemplo #1 Associatividade
<?php
$a = 3 * 3 % 5; // (3 * 3) % 5 = 4
$a = true ? 0 : true ? 1 : 2; // (true ? 0 : true) ? 1 : 2 = 2
$a = 1;
$b = 2;
$a = $b += 3; // $a = ($b += 3) -> $a = 5, $b = 5
?>
Nota: Mesmo tendo = menor precedência que que outros operadores, o PHP ainda permitirá expressões similares à seguinte: if (!$a = foo()), que no caso o retorno de foo() é recebido em $a.
Operadores
02-Aug-2008 06:30
13-Mar-2008 04:27
Thanks to phpnet dot 20 dot dpnsubs at xoxy dot net for this, it saved me a lot of time. The brackets sucks, but you can have fun with them - make smileys valid code :o)
$a = 2;
echo (
$a == 1 ? 'one' :(
$a == 2 ? 'two' :(
$a == 3 ? 'three' :(
$a == 4 ? 'four'
:0) ) )
);
14-Jan-2008 07:20
janturon at email dot cz wrote about shortening with "or"
$a = @$b or $a = 'undefined';
There's no reason to do this, because it generates a notice anyway. A better way to do this is
$a = isset($b) ? $b : 'undefined';
Note, that NULL value returns false when you use isset().
01-Nov-2007 06:13
Note that in php the ternary operator ?: has a left associativity unlike in C and C++ where it has right associativity.
You cannot write code like this (as you may have accustomed to in C/C++):
<?
$a = 2;
echo (
$a == 1 ? 'one' :
$a == 2 ? 'two' :
$a == 3 ? 'three' :
$a == 4 ? 'four' : 'other');
echo "\n";
// prints 'four'
?>
You need to add brackets to get the results you want:
<?
$a = 2;
echo ($a == 1 ? 'one' :
($a == 2 ? 'two' :
($a == 3 ? 'three' :
($a == 4 ? 'four' : 'other') ) ) );
echo "\n";
//prints 'two'
?>
10-Oct-2007 06:22
<?php
$result1 = 7 + 8 * 9/3 -4;
$result2 = 7 + 8 * (9/3 -4);
$result3 =(7 + 8)* 9/3 -4;
echo "Result1 for 7 + 8 * 9/3 -4 = $result1 Result2 for 7 + 8 * (9/3 -4) = $result2 and Result3 (7 + 8)* 9/3 -4 = $result3 "
/*
which gives results as under
Result1 for 7 + 8 * 9/3 -4 = 27 Result2 for 7 + 8 * (9/3 -4) = -1 and Result3 (7 + 8)* 9/3 -4 = 41
Execution Order is 1) expression in brackets 2) division 3) multiplication 4) addition and 5) subtraction
*/
?>
08-Oct-2007 09:42
This is very common problem: set one variable to another, if it is not empty. If it is, set it to something else.
For example: set $bar to $foo, if $foo is empty, set $bar to "undefined";
if(!empty($foo)) $bar= $foo; else $bar= "undefined";
OR operator can shorten it:
$bar= @$foo or $bar= "undefined";
12-Jul-2007 03:16
The scope resolution operator ::, which is missing from the list above, has higher precedence than [], and lower precedence than 'new'. This means that self::$array[$var] works as expected.
09-Jun-2007 06:17
In response to mathiasrav at gmail dot com:
The reason for that behavior is the parentheses. From the description:
"Parentheses may be used to force precedence, if necessary. For instance: (1 + 5) * 3 evaluates to 18."
So the order of operations says that even though the equality operator has higher precedence, the parentheses in your statement force the assignment operator to a higher precedence than the equality operator.
That said, it still doesn't work the way you expect it to. Neither way works, for these reasons:
<?php
if ( $a != ($a = $b) )
?>
Order of operations says to do the parentheses first. So you end up with:
<?php
$a = $b;
if ( $a != $a )
?>
Which is obviously going to be false. Without the parentheses:
<?php
if ( $a != $a = $b )
?>
Order of operations says to do the inequality first, then the assignment, so you have:
<?php
if ( $a != $a );
$a = $b;
?>
Which again is not what you expected, and again will always be false. But because you are only working with values of 0 and 1, you can make use of the XOR operator:
<?php
if ( $a ^= $b )
?>
This will only be true if 1) $a is 0 and $b is 1, or 2) $a is 1 and $b is 0. That is precisely what you wanted, and it even does the assignment the way you expected it to.
<?php
foreach ($ourstring as $c) {
if ($bold ^= $c['bold']) $resstring .= bold;
if ($underline ^= $c['underline']) $resstring .= underline;
$resstring .= $c[0];
}
?>
That code now works and produces the output you expected.
07-Apr-2007 12:41
<?php
"This might be related to the comment 31-Oct-2006 07:20 just below, but here goes.";
"I have found a bug (might be inherited from the way C does it) in PHP's operator precedence. Things like:";
if ($a != ($a = $b)) {/* more things */}
"doesn't work. In my code, I've changed that to:";
if ($a != $b) {$a = $b; /* more things */}
"A longer explanation (and a practical example) follows.";
"I've written an IRC bot which (among other things) can parse an IRC string and find out how the individual characters are formatted.";
// Quick guide to IRC formatting: In IRC, there are several 'format control characters', all non-printable. Among these are the bold formatting character, 0x02, which I'll write as <b>, and the underline formatting, 0x1F, which I'll write as <u>.";
"My code parses a string and reads these characters and makes an array which contains the individual characters and their formatting.";
"Here's an example. (I named the indices of the array, my code actually uses numbered indices)";
$ourstring = array(
array(
'Hello ',
'bold' => 1,
'underline' => 0,
), array(
'world.',
'bold' => 0,
'underline' => 1,
)
);
"And now, my formatparsedarray-to-ircstring function, that translates this to a string which can be posted to an IRC channel.";
$resstring = '';
define('bold', "\x02");
define('underline', "\x1F");
$bold = false;
$underline = false;
foreach ($ourstring as $c) {
if ($bold != ($bold = $c['bold'])) $resstring .= bold;
if ($underline != ($underline = $c['underline'])) $resstring .= underline;
$resstring .= $c[0];
}
"Now, $resstring should contain:";
$resstring == "\x02Hello \x02\x1Fworld.";
"However, it doesn't, since ($bold = $c\['bold'\]) is evaluated before ($bold == (...)). According to the operator precedence, == is evaluated left-to-right, and = is evaluated right-to-left, but in this case, == evaluated right-to-left.";
"Is this a bug, or is it a leftover from C's way of parsing such things?";
?>
In response to:
----------------------
T Chan
19-Aug-2006 10:30
[...]
In response to the manual, associativity doesn't determine the order of evaluation - it determines how it's "bracketed": a=b=c=1 is equivalent to a=(b=(c=1)), but a is evaluated first (an important point if evaluating a has side-effects)
<?php
function one($str) {
echo "$str";
return 1;
}
$a = array(1,2);
$a[one("A")] = $a[one("B")] = 1; // outputs AB
?>
----------------------
The manual, stated "associativity determines order of evaluation," which is completely correct, as it uses a stack execution, as with C.
The example you provided to counter the manual's statement however, is contrived, as it uses function calls to output a variable which is not even used in assignment; this in turn disproves (in your opinion) the manual's statement. Fuction calls, have much higher precedence than the assignment operator.
However:
Right Associativity with the '=' operator means the following:
The expression: $a = $b = 1;
IS indeed evaluated from right to left.
The stack is used as follows. (if you're not familiar with stacks / queues, look em up).
The expressions are pushed onto the stack in the following order:
$a $b = 1 =
^ ^
Bottom Top
The stack is then "evaluated" from top to bottom (which translates from right to left, if you're reading the expression)
It would read: assign 1 to assign $b to $a
Which results in $a = 1
Try the following simple script:
<?php
function output(& $b)
{
echo( "b value is: ".$b );
return $b;
}
$a = 2;
$b = 5;
echo ($a = $b = 1);
$a = 2;
$b = 5;
echo ( "a value is: ".$a = output($b) );
?>
Output is:
1
b value is: 5
a value is: 5
---------------------------------------
Your example had nothing to do with the assignment operator evaluation order, only procedural precedence.
20-Aug-2006 01:30
In response to 26-Mar-2001 08:53, parens don't need to have precedence. There's only one way to convert them to a syntax tree. I can't think of a sensible reason it could be ambiguous either (and sensible language designers will make ( always pair with ) so there can't be any ambiguity).
In response to 12-Aug-2005 08:47, you can do <?php $myvar OR ($myvar = 1); ?>, or the equivalent <?php !$myvar AND $myvar = 1; ?>, and if you have to use ifs, <?php if(!$myvar) { $myvar = 1; } ?> will do just fine (though in general, I'd be careful using boolean expressions as an indicator of success/failure when 0 could be a valid value. And you probably want to use isset($myvariable)).
In response to the manual, associativity doesn't determine the order of evaluation - it determines how it's "bracketed": a=b=c=1 is equivalent to a=(b=(c=1)), but a is evaluated first (an important point if evaluating a has side-effects)
<?php
function one($str) {
echo "$str";
return 1;
}
$a = array(1,2);
$a[one("A")] = $a[one("B")] = 1; // outputs AB
?>
09-Jul-2006 12:51
Simple POST and PRE incremnt sample:
<?php
$b = 5;
$a = ( ( ++$b ) > 5 ); // Pre-increment test
echo (int)$a;
$b = 5;
$a = ( ( $b++ ) > 5 ); // Post-increment test
echo (int)$a;
?>
This will output 10, because of the difference in post- and pre-increment operations
26-Nov-2005 06:30
Re: Rick on 2-Sep-2005.
Actually, the C equivalent of "$a[$c++]=$b[$c++];" has undefined behavior, and the increments are by no means guaranteed to happen after the assignment in C. (Search for a discussion of C "sequence points" for details.)
02-Sep-2005 08:15
Note the highly unfortunate difference from Java, which associates the trinary operator right-to-left.
---------------------------- source
function trinaryTest($foo){ // works as you think in Java, but not PHP
$bar = $foo > 20
? "greater than 20"
: $foo > 10
? "greater than 10"
: $foo > 5
? "greater than 5"
: "not worthy of consideration";
echo $foo." => ".$bar."\n";
}
echo "\n\n\n----trinaryTest\n\n";
trinaryTest(21);
trinaryTest(11);
trinaryTest(6);
trinaryTest(4);
function trinaryTestParens($foo){
$bar = $foo > 20
? "greater than 20"
: ($foo > 10
? "greater than 10"
: ($foo > 5
? "greater than 5"
: "not worthy of consideration"));
echo $foo." => ".$bar."\n";
}
echo "\n\n\n----trinaryTestParens\n\n";
trinaryTestParens(21);
trinaryTestParens(11);
trinaryTest(6);
trinaryTestParens(4);
---------------------------- output
----trinaryTest
21 => greater than 5
11 => greater than 5
6 => greater than 5
4 => not worthy of consideration
----trinaryTestParens
21 => greater than 20
11 => greater than 10
6 => greater than 5
4 => not worthy of consideration
02-Sep-2005 06:51
A quick note to any C developers out there, assignment expressions are not interpreted as you may expect - take the following code ;-
<?php
$a=array(1,2,3);
$b=array(4,5,6);
$c=1;
$a[$c++]=$b[$c++];
print_r( $a ) ;
?>
This will output;-
Array ( [0] => 1 [1] => 6 [2] => 3 )
as if the code said;-
$a[1]=$b[2];
Under a C compiler the result is;-
Array ( [0] => 1 [1] => 5 [2] => 3 )
as if the code said;-
$a[1]=$b[1];
It would appear that in php the increment in the left side of the assignment is processed prior to processing the right side of the assignment, whereas in C, neither increment occurs until after the assignment.
22-Aug-2005 08:38
D'oh! please ignore (& forgive) the first paragraph in my note yesterday - I said that a diadic operator had the same precedence & associativity as a bunch of monadics. A bit of early senility must have struck me.
When I find time I'll rework my test to find out what I should have said - but using instanceof monadically didn't cause any visible errors in the test, so it could take a while.
[I'd be delighted if someone else beats me to it/ spares me the difficulties of seeing what's wrong in something that shouldn't have worked.]
21-Aug-2005 12:21
Table 15-1 omits the precedence of instanceof - testing suggests it to be of the same precedence as not, negate, casting, and @.
The table also omits the precedence (and associativity) of the "execution operator" - but since that's a sort of quoting, I don't think it meaningfully has a precedence or associativity - they explain what is to happen where there's an open-endedness in the sense of missing brackets, and the quoting is a sort of bracket. (At least: because of the execution operator's double-ended closedness, I can't figure out any code where it would matter, so I can't test it.)
12-Aug-2005 03:47
I regularly use some syntax like :
<?php
if(!$myvar)
$myvar = $value ;
?>
and
<?php
if($myvar)
echo "myvar is $myvar today" ;
?>
(or <?php echo ($myvar ? "myvar is $myvar today" : "") ?>)
It's small, but can become heavy when used too much.
Isn't there some trick to better such syntaxes ?
I was wondering about using things like :
<?php $myvar ||= $value ; ?>
<?php $myvar ?= $value ; ?>
<?php echo ($myvar ? "myvar is $myvar today") ; ?>
04-May-2005 01:26
In response to npeelman at cfl dot rr dot com
29-Dec-2004 06:22:
You have misunderstood the behaviour of the interpreter.
With out the curly braces and the single quoted key identifier, the interpreter "assumes" you meant your CONSTANT to be a string. This ONLY works within a parsed (double quoted) string. And it doesn't help you at all if your array is multi-dimensional. I consider this a very bad habbit because it will get you in trouble elsewhere. Try the following:
<?php
define('item','AnyOldThing');
define('b',12);
$arr['item']['b'] = 'string';
$arr['AnyOldThing'][12]= 'Maybe not what I intended.';
echo "This is a {$arr['item']['b']}"; // [1] prints "This is a string".
echo "This is a $arr[item][b]"; // [2] broken
echo $arr[item][b]; // [3] broken
?>
29-Dec-2004 06:22
Update to message by yasuo_ohgaki at hotmail dot com:
I know this is an old message but when using an Associative array in a string you do not have to use { and } to resolve ambiguity.
ex:
Associative Array in string:
$arr['item'] = 'string';
echo "This is {$arr['item']}"; //prints "This is string".
...does work but, so does:
echo "This is $arr[item]"; //prints "This is string".
... simply enclose the whole string with double quotes and leave out the single quotes from around the index name. This simplifies the code and makes things easier to read.
01-Sep-2004 04:33
The low precedence of the OR operator is useful for error control statements such as this one:
$my_file = @file ('non_existent_file') or die ("Failed opening file: error was '$php_errormsg'");
Notice the good readability of the code.
I think warhog's note about the differing precedence between && / AND and || / OR is worth repeating. Since && and || evaluate before the assignment operator (=) while AND and OR evaluate after it, you can get COMPLETELY different results if you don't fully parenthesise.
I cannot imagine when it would ever be important that those two pairs have differing precedence, but they do. And I just spent two hours discovering that the hard way because I broke my career-long rule:
*Always fully parenthesise!*
Warhog wrote: "maybe usefull for some tricky coding and helpfull to prevent bugs :D"
I'm sure Warhog was being facetious, but for the new programmers in the audience I'd like to point out that 'tricky coding' and relying on precedence/order of evaluation are both well-known ways to *produce* bugs.
Use parentheses instead.
of course this should be clear, but i think it has to be mentioned espacially:
AND is not the same like &&
for example:
<?php $a && $b || $c; ?>
is not the same like
<?php $a AND $b || $c; ?>
the first thing is
(a and b) or c
the second
a and (b or c)
'cause || has got a higher priority than and, but less than &&
of course, using always [ && and || ] or [ AND and OR ] would be okay, but than you should at least respect the following:
<?php $a = $b && $c; ?>
<?php $a = $b AND $c; ?>
the first code will set $a to the result of the comparison $b with $c, both have to be true, while the second code line will set $a like $b and THAN - after that - compare the success of this with the value of $c
maybe usefull for some tricky coding and helpfull to prevent bugs :D
greetz, Warhog
26-Mar-2001 03:34
About "{" and "}".
Sometimes PHP programmers need to use "{" and "}" to resolve ambiguity. Here is some examples.
Variable Variables:
<?php
$foo = "test";
$$bar = "this is";
echo "${$bar} $foo"; // prints "this is test"
?>
Note: it is the same as
<?php echo "$test $foo"; ?>
Array in string:
<?php
$arr[10][10][10] = "string";
echo "This is {$arr[10][10][10]}"; // prints "This is string"
?>
Associative Array in string:
<?php
$arr['item'] = 'string';
echo "This is {$arr['item']}"; //prints "This is string".
?>
26-Mar-2001 02:53
Other Language books' operator precedence section usually include "(" and ")" - with exception of a Perl book that I have. (In PHP "{" and "}" should also be considered also). However, PHP Manual is not listed "(" and ")" in precedence list. It looks like "(" and ")" has higher precedence as it should be.
Note: If you write following code, you would need "()" to get expected value.
<?php
$bar = true;
$str = "TEST". ($bar ? 'true' : 'false') ."TEST";
?>
Without "(" and ")" you will get only "true" in $str.
(PHP4.0.4pl1/Apache DSO/Linux, PHP4.0.5RC1/Apache DSO/W2K Server)
It's due to precedence, probably.
