Edit report at https://bugs.php.net/bug.php?id=52412&edit=1

 ID:                 52412
 Comment by:         denis at slik dot eu
 Reported by:        madboyka at yahoo dot com
 Summary:            __autoload fails to throw exception when calling a
                     static method on the class
 Status:             Not a bug
 Type:               Bug
 Package:            Scripting Engine problem
 Operating System:   *
 PHP Version:        5.3.3
 Block user comment: N
 Private report:     N

 New Comment:

Can't reproduce this anymore on 5.4.3.
Good riddance.


Previous Comments:
------------------------------------------------------------------------
[2012-06-10 17:54:19] rahuijts at tiscali dot nl

Please
- explain (and let the documentation show) why it is not possible to throw an 
exception in the __autoload function if a static call is made on a non-existing 
class, when it is possible to do so if a non-existing class is instantiated,
- or reopen this bug report to acknowledge that it should be possible in both 
cases but currently fails for static calls due to a bug in PHP.

The documentation indeed supports the case for this bug report, but to defend 
der...@php.net as well: the first part of his response is probably a template 
text when marking a report as "Not a bug". The rest of his message does not 
mention static calling, which is essential for the problem to occur, so I think 
he closed the report because he missed that point. Please let us know, because 
the current status is very confusing.

------------------------------------------------------------------------
[2011-02-21 19:35:10] php dot net at phrozenbyte dot de

I support this re-opening-request... Since 5.3 __autoload() is definitly *not* 
"the last line of defense for PHP to find a class definition". That's simply 
wrong.

http://www.php.net/manual/en/language.oop5.autoload.php (Note #1 + Example #3)
http://www.php.net/manual/en/language.oop5.changelog.php (#5)

------------------------------------------------------------------------
[2011-02-19 23:06:12] michael at squiloople dot com

Here's a request to re-open the bug, for it is indeed a bug: exceptions can be 
thrown and caught if the method called is _not_ static, as documented, but 
cannot 
be thrown and caught if the method _is_ static (and where the class name is not 
a 
variable), which is both inconsistent and against the documentation. It is 
_unexpected_ behaviour.

------------------------------------------------------------------------
[2011-02-16 15:31:49] madboyka at yahoo dot com

To: der...@php.net
I don't think you've read the documentation on autoloading yourself:
http://www.php.net/manual/en/language.oop5.autoload.php

The first note states that since PHP 5.3, you may throw an exception from the 
autoload function (even if the class can be loaded) and catch that exception 
without a problem. Examples #3 and #4 in the documentation entry demonstrate 
this. This works when the autoload function gets invoked when instantiating a 
class, but doesn't when you make a static call on it. This behavior is not 
consistent.
Also, take a look at michael@...'s workaround, which unexpectedly works great. 
And don't tell me that PHP behaves as "expected".

I understand, that this is not a major bug, we all can live without a fix, but 
at least mark it as to be fixed in the far future.

------------------------------------------------------------------------
[2011-02-16 11:24:38] der...@php.net

Thank you for taking the time to write to us, but this is not
a bug. Please double-check the documentation available at
http://www.php.net/manual/ and the instructions on how to report
a bug at http://bugs.php.net/how-to-report.php

FWIW, this is "expected". The __autoload() method is the last line of defense 
for PHP to find a class definition. If it can't find it, PHP bails out with a 
fatal error. If you throw an exception, you basically abort this final chance, 
and thus gives PHP you that fatal "can not find class" error. However, you can 
catch the exception in the __autoload() method,

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


The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at

    https://bugs.php.net/bug.php?id=52412


-- 
Edit this bug report at https://bugs.php.net/bug.php?id=52412&edit=1

Reply via email to