#38504 [Bgs]: class_exists strange behaviour
| From: | kn1g at yahoo dot com dot br | Date: | Sat, 19 Aug 2006 02:45:09 +0000 |
| Subject: | #38504 [Bgs]: class_exists strange behaviour | ||
| References: | 1 | Groups: | php.bugs |
| Request: | Send a blank email to php-bugs+get-100951@lists.php.net to get a copy of this message | ||
ID: 38504
User updated by: kn1g at yahoo dot com dot br
Reported By: kn1g at yahoo dot com dot br
Status: Bogus
Bug Type: Class/Object related
Operating System: Linux
PHP Version: 4.4.4
New Comment:
I see, well, I think that class_exists function manual could have a
note warning about this (I didn't find this information anywhere).
Previous Comments:
------------------------------------------------------------------------
[2006-08-18 20:38:56] tony2001@php.net
Classes are declared during the compile time.
So the class DOES exist and when you actually run the code, the if
condition evaluates to TRUE, hence return is executed.
This is expected behaviour.
------------------------------------------------------------------------
[2006-08-18 18:27:15] kn1g at yahoo dot com dot br
Description:
------------
class_exists with return appears to avoid setting a variable after a
class definition.
Avoiding the return inside the if block like work as expected:
<?
if(!class_exists('newclass')){
class newclass(){
}
}
$var_newclass = "newclass ok\n";
?>
But I couldn't find anything in the documentation explaining this
behaviour.
Reproduce code:
---------------
"class.php"
<?
if(class_exists('newclass')){
return;
}
class newclass{
function newclass(){
echo "hi\n";
}
}
$var_newclass = "newclass ok\n";
?>
"test.php"
<?
include("class.php");
new newclass;
echo $var_newclass;
?>
Expected result:
----------------
hi
newclass ok
Actual result:
--------------
hi
------------------------------------------------------------------------
--
Edit this bug report at http://bugs.php.net/?id=38504&edit=1