Newsgroups: php.doc,php.internals
Path: news.php.net
Xref: news.php.net php.doc:969379109 php.internals:39060
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain iamjochem.com from 194.109.193.121 cause and error)
Message-ID: <487F8379.4070801@iamjochem.com>
Date: Thu, 17 Jul 2008 19:38:01 +0200
User-Agent: Thunderbird 2.0.0.14 (Macintosh/20080421)
MIME-Version: 1.0
To: Marcus Boerger <helly@php.net>
CC: Derick Rethans <derick@php.net>, 
 Gergely Hodicska <felho@avalon.aut.bme.hu>,
 PHP Documentation List <phpdoc@lists.php.net>, 
 "internals@lists.php.net" <internals@lists.php.net>
References: <4875821E.9020504@avalon.aut.bme.hu> <20080710045418.GA22262@panix.com> <487599FA.9000207@avalon.aut.bme.hu> <alpine.DEB.0.98.0807100925140.19858@kossu.ez.no> <4875CE7F.9090308@avalon.aut.bme.hu> <alpine.DEB.0.98.0807101059320.19858@kossu.ez.no> <48764379.3010304@iamjochem.com> <1672378551.20080712122931@marcus-boerger.de> <487F18FE.1070600@iamjochem.com> <1929951966.20080717131829@marcus-boerger.de>
In-Reply-To: <1929951966.20080717131829@marcus-boerger.de>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] strange autoload behavior
From: jochem@iamjochem.com (Jochem Maas)

Marcus Boerger schreef:
> Hello Jochem,
> 

...

>> I just posted another mail to internals in which I attempt to detail the
>> __autoload behaviour 'issues' ... it includes something that wants to be a
>> test suite when it grows up ... it might help someone to investage/determine
>> what __autoload() does/should do:
> 
>> http://iamjochem.com/autoload_behaviour_tests.zip
> 
> Great! More tests :-)
> 
> It is quite a lot of stuff and I'd like to see this turned into .phpt's.

it looks more than it is, the runtests.sh script makes viewing the results
of the variations in settings/code easier.

if you unzip the file and execute ./runtests.sh with no args it goves you
all the options ... at this stage I wrote primarily to figure out what
actually happens under any number of conditions.

I'd love to take a shot at converting them to .phpt I see 3 problems

1. I don't know .phpt (I can solve this)
2. I have no idea what to expect and therefore test for
    (this needs to be determined/clarified!)
3. In the case that I need to test for an uncaught Exception I wonder
    how to determine a pass (ie uncaugh exception thrown as expected) given
    that the exact output is dependent on the full path of the relevant script

any advice as to how to proceed, especially with regard to point 2.

rgds,
Jochem

> 
> marcus
> 
>>> That is they
>>> are simply ignored. 
> 
>> and so I thought :-) which is why some of my test's output "wtf!" :-)
> 
>> as always, thanks for your feedback,
>> regards,
>> Jochem
> 
>>> And once all __autoload work is done and the class
>>> still doesn't exist an E_ERROR is issued. The work around for cases where
>>> the class must not exist (e.g. when no E_ERROR is needed would be
>>> collecting the exceptions. That is the base Exception class would get an
>>> additional property and getter:
>>>   private $previous_exception;
>>>   function public getPreviousException();
>>> That way we could let the exceptions bubble up (though some smaller engine
>>> changes are necessary).
> 
>> currently you can throw an exception out of __autoload() unless __autload()
>> is triggered by the 'new' syntax or by a static method call (e.g. MyClass::myMethod()),
>> with other 'triggers' (e.g. call_user_func()) the exception comes through ...
>> in cases that it doesn't you can get an exception out of __autoload() via the
>> eval() trick [see below] ... I don't suppose there is anyway of asking the engine
>> which way __autoload() was triggered from inside the __autoload() code?
> 
>>> marcus
>>>
>>> Thursday, July 10, 2008, 7:14:33 PM, you wrote:
>>>
>>>> Derick Rethans schreef:
>>>>> On Thu, 10 Jul 2008, Gergely Hodicska wrote:
>>>>>
>>>>>>> exceptions thrown during autoload are ignored.
>>>>>> And one more thing, this is in the manual:
>>>>>> "Note: Exceptions thrown in __autoload function cannot be caught in the catch
>>>>>> block and results in a fatal error."
>>>>>>
>>>>>> I think your explanation makes much more clear what happens, maybe it would
>>>>>> worth to upgrade the manual. While the quoted text suggests that that if throw
>>>>>> an exception I just can't catch it and will bubble up to top level and this
>>>>>> cause the fatal error.
>>>>> You can actually catch it *in* the autoload method, it just wouldn't 
>>>>> bubble out of it.
>>>> the manual could do with that tidbit, maybe also the hack for 'getting the
>>>> exception out' of __autoload() ...
>>>>         function __autoload($class)
>>>>         {
>>>>                 try {
>>>>                         throw new Exception('foo');
>>>>                 } catch (Exception $e) {                                
>>>>                     self::handleDebug($e);
>>>>                 
>>>>                     if (!class_exists($class, false))
>>>>                         eval(sprintf('
>>>>                      class %1$s
>>>>                      {
>>>>                          public         function __construct()        {
>>>> throw new AL_Exception("Class %1$s not found: %2$s"); }
>>>>                          public         function __call($m, $a)       {
>>>> throw new AL_Exception("Class %1$s not found: %2$s"); }
>>>>                          public  static function __callStatic($m, $a) {
>>>> throw new AL_Exception("Class %1$s not found: %2$s"); }
>>>>                      }', $class, $e->__toString()));                    
>>>>                 }
>>>>         }
>>>> which works best when __autoload() isn't triggered by class_exists("Foo", true)
>>>
>>>>> regards,
>>>>> Derick
>>>>>
>>>
>>>
>>>
>>>
>>> Best regards,
>>>  Marcus
>>>
>>>
> 
> 
> 
> 
> Best regards,
>  Marcus
> 
>