Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:56624
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.214.42 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <ef077b1efd9e0b03e64d69e1f50b4ff1@mohiva.com>
References: <4ECEC513.9040706@mohiva.com> <EA.C2.16974.AC24FCE4@pb1.pair.com>
 <06acba1a1c53ac9527beb807787c92aa@mohiva.com> <CA+S5htNo4vm9wR0p385eTsF20cdvLooVnW7Bg+-H992TCk7JWw@mail.gmail.com>
 <ef077b1efd9e0b03e64d69e1f50b4ff1@mohiva.com>
Date: Fri, 25 Nov 2011 08:00:16 -0200
Message-ID: <CA+S5htN3WC7sAx=qSajw=_EAadk6ZfFP=6ETD6d5Uc51biDbrA@mail.gmail.com>
To: Christian Kaps <christian.kaps@mohiva.com>
Cc: internals@lists.php.net
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] Re: [RFC] Autoloader Error Handling
From: kassner@gmail.com (Rafael Kassner)

If your autoloader throws an exception, you need to try/catch entire
application. It doesn't sounds useful. On my view, if you want to be
mailed about an autoloader fail, this have to be coded inside of your
own single autoloader.

On Fri, Nov 25, 2011 at 7:46 AM, Christian Kaps
<christian.kaps@mohiva.com> wrote:
> Am 25.11.2011 10:34, schrieb Rafael Kassner:
>>
>> I think an autoloader can't be raise any kind of error. If the class
>> will be loaded by another autoloader on the stack and the first throws
>> an Exception, this will be a wrong behavior.
>> Indeed, if autoloader can't include the class, PHP throws a fatal
>> error, and you can avoid it using class_exists function that calls
>> autoloader by its own.
>
> You can do this, but the engine triggers still a fatal error. The call "n=
ew
> NotExistingClass();" triggers the autoloader. The autoloader sees that th=
e
> class doesn't exists and continues silent. And now the engine tries to
> instantiate a not existing class, which ends in a fatal error.
>
>
>> On Fri, Nov 25, 2011 at 6:06 AM, Christian Kaps
>> <christian.kaps@mohiva.com> wrote:
>>>
>>> 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 clas=
s
>>> couldn't be loaded. I do this by adding a try/catch block around my cod=
e.
>>>
>>> try {
>>> =A0 =A0new Application();
>>> } catch (Exception) {
>>> =A0 =A0// collect data
>>> =A0 =A0// send mail
>>> =A0 =A0// 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
>>>
>>> --
>>> PHP Internals - PHP Runtime Development Mailing List
>>> To unsubscribe, visit: http://www.php.net/unsub.php
>>>
>>>
>>
>>
>>
>> --
>> Atenciosamente,
>> Rafael Kassner
>
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>



--=20
Atenciosamente,
Rafael Kassner