Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:62799
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.213.170 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <50453FB4.3070606@lerdorf.com>
References: <AANLkTimWuPXCs-HT6RgQYmH7UKcOYXkeTiMEnBwBXxnt@mail.gmail.com>
	<CAH-PCH4YdBr7WfQ2PR0_Fr_C=TfBsSGsbX3G-jonUqyfLrCcZQ@mail.gmail.com>
	<5040DC47.8000305@ajf.me>
	<CAH-PCH5TM2ag-5xm3Rk7Ef6LnpEst1UqRoc_f_Uwp_aLe418dA@mail.gmail.com>
	<5040F4D9.80206@sugarcrm.com>
	<CAEZPtU6X9gLRALzA+KGKNoF5c7ey-xgJ=0NhjF2qVfD9YJqN+Q@mail.gmail.com>
	<5042946A.80204@sugarcrm.com>
	<op.wjzdwn08idpuyk@damnation.nl.lo.geleia.net>
	<5042A7D6.7050001@lerdorf.com>
	<op.wjzgbuh1idpuyk@damnation.nl.lo.geleia.net>
	<alpine.DEB.2.02.1209031214250.25835@whisky.home.derickrethans.nl>
	<a565e97fdd574cebf2baca1c54c425a2@nebm.ist.utl.pt>
	<50452713.3020307@sugarcrm.com>
	<b6bf26cb6b4d2392d5fd13237669a19d@nebm.ist.utl.pt>
	<CAKZjf5Q0CBE_0_+1mpko0ePbkptFtx7aohczou4kOcnoCdSZtA@mail.gmail.com>
	<50453FB4.3070606@lerdorf.com>
Date: Tue, 4 Sep 2012 17:05:44 +0200
Message-ID: <CAKZjf5SF7_0jThGZ_J3LTCpg9sXW1OJ9DGWxoPa52vh9aOyAsw@mail.gmail.com>
To: Rasmus Lerdorf <rasmus@lerdorf.com>
Cc: Gustavo Lopes <glopes@nebm.ist.utl.pt>, internals@lists.php.net
Content-Type: text/plain; charset=ISO-8859-1
Subject: Re: [PHP-DEV] Re: Are exceptions allowed in php core?
From: alex.aulbach@gmail.com (Alex Aulbach)

2012/9/4 Rasmus Lerdorf <rasmus@lerdorf.com>:
> On 09/03/2012 04:31 PM, Alex Aulbach wrote:
>> 2012/9/4 Gustavo Lopes <glopes@nebm.ist.utl.pt>:
>>>> Following this logic, we'd have to convert all E_NOTICE and E_STRICT to
>>>> fatal errors or exceptions - they are usually produced by programming
>>>> errors and aren't meant to be caught by surrounding code (actually,
>>>> can't). But I don't see anybody benefiting from this - as I don't see
>>>> anybody benefiting from generator that will explode your application if
>>>> you touch it twice.
>>
>> Nobody is forced to handle an notice-exception like a fatal exception.
>> A notice-exception can be created write something into an error-log
>> and tells PHP not to handle it any more (destroys itself). Could be
>> all done in the construction of the exception.
>>
>
> First, you got the quoting wrong. Please be more careful with that.

Sorry, was written from very old laptop which has problems, when I mark text.

> And second, huh? Uncaught exceptions are by definition fatal. There is
> no such thing as a notice exception. If we go down that road refer to my
> email describing condition error systems. Longer term I think a
> condition system would make a lot of sense for PHP, but we definitely
> don't want to introduce some sort of bastard non-fatal exception.

Maybe I had not the right words to describe, what I mean: I would like
to see both worlds (current error-handling and exceptions) in PHP -
just as I need it.

Your proposal sounds quite interesting. For example: If an SQL-query
fails, the query itself isn't normally very interesting (it's wrong,
ok). I need to know where it was created and how. The error is not in
the database, it's most times in the PHP-program...


-- 
Alex Aulbach