[PHP-DEV] PHP 4.0 Bug #8139 Updated: NULL and isset From: richard.heyes <email protected>
Date: 12/07/00

ID: 8139
User Update by: richard.heyes <email protected>
Old-Status: Feedback
Status: Open
Bug Type: Scripting Engine problem
Description: NULL and isset

No idea. Though I do know of people who use that method to set variables, so their answer would be a resounding no. :)

(EG:
<?php
function mconnect(&$link){
    $link = mysql_connect();
}

mconnect($db);
?>
)

Previous Comments:
---------------------------------------------------------------------------

[2000-12-06 13:18:04] joey <email protected>
The question is: should passing an unset variable by reference
generate a warning?

---------------------------------------------------------------------------

[2000-12-06 12:57:39] richard.heyes <email protected>
<?php
function foo(&$bar){
    return TRUE;
}

foo($bar);

print($bar);

if(!isset($bar))
    print('Bar is not set!');
?>

With notices turned on (error_reporting) the call to print($bar) does not throw an error. However the bit below it runs the print() call. So if it's not set, the first print should throw an error regarding the unset $bar. Seems very contradictory. FWIW the type of $bar after the call to foo() is NULL.

---------------------------------------------------------------------------

Full Bug description available at: http://bugs.php.net/?id=8139 

-- 
PHP Development Mailing List <http://www.php.net/>
To unsubscribe, e-mail: php-dev-unsubscribe <email protected>
For additional commands, e-mail: php-dev-help <email protected>
To contact the list administrators, e-mail: php-list-admin <email protected>