Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:56273
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain mohiva.com from 80.67.31.35 cause and error)
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8;
 format=flowed
Content-Transfer-Encoding: 7bit
Date: Fri, 11 Nov 2011 09:52:34 +0100
To: <internals@lists.php.net>
In-Reply-To: <CAAyV7nG91GeszEnmhmPVVvsYp5tP3BR9aOE3QWXAQvjLFjzK+g@mail.gmail.com>
References: <CAAyV7nEi+1XzYryoE9tg48jZMMPe1psz=VWDkGSzEgAwBKs9pw@mail.gmail.com>
 <CAFp73XuQGG9mEZUZ2OK1yLkBiFDcPwOxytQ80D=xZUafEv20tw@mail.gmail.com>
 <CAAyV7nG91GeszEnmhmPVVvsYp5tP3BR9aOE3QWXAQvjLFjzK+g@mail.gmail.com>
Message-ID: <9274e90a58f9a9cffee6a2d9922e6ff9@mohiva.com>
User-Agent: Roundcube Webmail/0.6
Subject: Re: [PHP-DEV] Re: SPLClassLoader RFC Thoughts And Improvements
From: christian.kaps@mohiva.com (Christian Kaps)

Hi

.. snip ..

>> Hm... so there should never have the normal available?
>> I need to think over this again then. While I tend to agree with
>> autoloader never triggering errors or exceptions, the debug mode is
>> the unique way to notice if user during developer haven't done any
>> mistake.
>> Maybe we can only keep the RuntimeException and debug mode
>> possibility, remove the normal and keep it always silent. What do 
>> you
>> think?
>
> I think that an exception to this request could be made for the DEBUG
> mode (as the way you're doing it is pretty much the only way you 
> could
> identify that).  Perhaps changing the exception to a warning or 
> notice
> (as you wouldn't want that in prod), but I could live with the error
> in debug mode as it shouldn't be used outside of testing and dev 
> work.
>  I was more referring to errors/exceptions in normal usage...
>

Would it not be possible that the autoloader mechanism catch all 
exceptions made by any autoloader which fails to load a class. Only if 
none of the register autoloaders can load the requested class the 
autoloader mechanism throws an AutoloadException with all the catched 
exceptions. This behaviour should be controllable by the users 
environment. So if using an autoloader(e.g. from a library) which throws 
an exception, but the user doesn't use exceptions in his environment, he 
should be able to deactivate the exceptions thrown by the autoloader 
mechanism. I think this behaviour has the greatest advantages for both 
worlds. This one which needs exceptions to shut down the application in 
an ordered way, and for these relying on PHPs way to handle the 
autoloading error.

Cheers