Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:56615
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain mohiva.com from 80.67.31.26 cause and error)
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8;
 format=flowed
Content-Transfer-Encoding: 7bit
Date: Fri, 25 Nov 2011 09:06:33 +0100
To: <internals@lists.php.net>
In-Reply-To: <EA.C2.16974.AC24FCE4@pb1.pair.com>
References: <4ECEC513.9040706@mohiva.com>
 <EA.C2.16974.AC24FCE4@pb1.pair.com>
Message-ID: <06acba1a1c53ac9527beb807787c92aa@mohiva.com>
User-Agent: Roundcube Webmail/0.6
Subject: Re: [PHP-DEV] Re: [RFC] Autoloader Error Handling
From: christian.kaps@mohiva.com (Christian Kaps)

Am 25.11.2011 08:24, schrieb Michael Wallner:
> On Thu, 24 Nov 2011 23:28:35 +0100, Christian Kaps wrote:
>
>>
>> https://wiki.php.net/rfc/autoloader_error_handling
>>
>
> Throwing an exception or fatal error in an autoloader
> absolutely does not make any sense in my eyes.
> Projects doing this should step back and think a
> minute about what they dare.
>
> Mike

Hi,

how would you bring your application in a consistent state after a 
class couldn't be loaded. I do this by adding a try/catch block around 
my code.

try {
     new Application();
} catch (Exception) {
     // collect data
     // send mail
     // redirect to maintenance page
}

An other question is, if the autoloader work silent and I write:

new NotExistingClass();

I think in this case the engine will also trigger a fatal error. So in 
my eyes it is regardless of whether it trigger a fatal error in the 
autoloader or the autoloader works silent. Both cases ends in a fatal 
error. Or am i wrong here?

Christian