Actually Todd, ...
> There is no way to call a function
> before doing the work in the argument list. If I call f(1+2),
> I can be sure the computation to get 3 will be performed
> _before_ calling f. The issue with f($p=array()) is that
> "$p=array()" is an r-value.
...that is theoretically ve
in that case, the documentation on socket_select() needs to be edited:
http://www.php.net/socket-select says:
0) {
/* At least at one of the sockets something interesting happened */
}
?>
according to you, $write and $except could be undefined, right?
- Ron
"Johannes Schlueter" <[EMAIL PR
It looks like
http://www.php.net/manual/en/language.operators.assignment.php
could use a bit of updating. A paragraph about php 5 or a
link to the semantics changes for php 5 would help newbies.
The text about php4 says there is copy on assignment, which
implies a performance hit for using = inste
Hi,
On Monday 24 July 2006 17:52, Rishad Omar wrote:
> getArray($p = array());
Here you are relying on undefined behavior. It is not defined wether $p =
array() or the function call getarray($p) should be executed first so the
order might always change.
You should always use the two lines
On Monday 24 July 2006 10:52, Rishad Omar wrote:
> Hello,
>
> I've upgraded from 5.1.1 to 5.1.2 and discovered the following
> unexpected difference. Best shown by example.
>
> function getArray(&$arr)
> {
> $arr[] = 12;
> }
>
> getArray($p = array());
> print_r($p);
>
