Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:62806
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.160.42 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <50463317.7000109@lerdorf.com>
References: <AANLkTimWuPXCs-HT6RgQYmH7UKcOYXkeTiMEnBwBXxnt@mail.gmail.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>
	<5045CAA3.6000409@lsces.co.uk>
	<CAEZPtU77K_wdRErqEQ1ZXj1_sWY2N_UcNkZsL5_h3UfjDmQK1Q@mail.gmail.com>
	<5045E044.9080809@lsces.co.uk>
	<CAL+t6cHD05znYaq7iPNwFNem=zma0-htbPG-Fc3550U-s5jcRA@mail.gmail.com>
	<5045F939.6010806@lsces.co.uk>
	<CAEZPtU4POFm-WJBuYj=bWLMqwtHEViVaZ_2XkE5W3CJfg7uPAg@mail.gmail.com>
	<5045FD98.8080306@lsces.co.uk>
	<CAH-PCH774j+9sV4Oq2Q66BTjRTsd9QtPu5Dnjsf-c_Zg_3nK9w@mail.gmail.com>
	<CAC6CJqbmh0vkSzrjj=miRz2hwVgk6fVPnwPw2wmhykKJZrKUGA@mail.gmail.com>
	<50463317.7000109@lerdorf.com>
Date: Tue, 4 Sep 2012 19:34:12 +0200
Message-ID: <CAH-PCH4AMGiJotNsajr-Q3cxN+k_Xn_1ebTdb9jX8M5GoVcKDw@mail.gmail.com>
To: Rasmus Lerdorf <rasmus@lerdorf.com>
Cc: Adam Richardson <simpleshot@gmail.com>, PHP Development <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=047d7b2ee2e9bedf5c04c8e3aa1f
Subject: Re: [PHP-DEV] E_STRICT 'errors' - was Are exceptions allowed in php core?
From: tyra3l@gmail.com (Ferenc Kovacs)

--047d7b2ee2e9bedf5c04c8e3aa1f
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

2012.09.04. 18:58, "Rasmus Lerdorf" <rasmus@lerdorf.com> ezt =C3=ADrta:
>
> On 09/04/2012 09:36 AM, Adam Richardson wrote:
> > I think Ferenc is correct in that this sounds like there's a custom
> > error handler somewhere. If the custom error handler collects error
> > info and then throws an exception (as has been detailed in various
> > blog posts as one manner of unifying the errors), this would cause the
> > trouble you're seeing.
>
> Only on a new E_STRICT. Even with E_STRICT off by default, custom error
> handlers are still called, and I think Lester said that turning E_STRICT
> off made it work. So if this is the cause, then it has nothing to do
> with E_STRICT being in E_ALL or not, nor whether display_errors is on or
> off. It would have to do with the custom error handler blowing up on one
> specific E_STRICT, which I find rather unlikely.
>

Don't forget that many error handlers check the error level against the
currently set error_reporting (so that they won't be executed on supressed
errors and such).
AFAIR we even promote that implementation in our error handler example in
our docs.
That would mean that the error handler main logic is only executed if
E_STRICT is in the error_reporting.

--047d7b2ee2e9bedf5c04c8e3aa1f--