Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:62794
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: <5045FD98.8080306@lsces.co.uk>
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>
	<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>
Date: Tue, 4 Sep 2012 15:43:41 +0200
Message-ID: <CAH-PCH774j+9sV4Oq2Q66BTjRTsd9QtPu5Dnjsf-c_Zg_3nK9w@mail.gmail.com>
To: Lester Caine <lester@lsces.co.uk>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=047d7b2e09d7365e8004c8e0726d
Subject: Re: [PHP-DEV] E_STRICT 'errors' - was Are exceptions allowed in php core?
From: tyra3l@gmail.com (Ferenc Kovacs)

--047d7b2e09d7365e8004c8e0726d
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Tue, Sep 4, 2012 at 3:09 PM, Lester Caine <lester@lsces.co.uk> wrote:

> Pierre Joye wrote:
>
>> On Tue, Sep 4, 2012 at 2:51 PM, Lester Caine<lester@lsces.co.uk>  wrote:
>>
>>  >??? OH YES IT DOES !!!
>>> >MANY times I get a a few lines of text on a white screen ...
>>> >Switch off E_STRICT and everything works fine ... as it was on PHP5.2
>>>
>> If you have any doubts about how to configure your development or
>> production servers, how to use logs or how to effectively debug php
>> applications, please ask questions on php-general or php-setup mailing
>> lists.
>>
>> Thanks for your understanding,
>>
> Butt out Pierre ...
>
> I keep being told that there is nothing wrong with E_STRICT, and again
> someone has said that it does NOT cause crashes. I beg to differ here - I=
T
> DOES!
>

never heard of that one before.

for example, running
<?php
for($i=3D0;$i<100;$i++){
  $foo=3D"foo_".$i;
  ${$foo}->bar =3D 123;
}
echo "done";

gives me 100 E_STRICT, but still executes just fine and prints "done" at
the end.
the only explanation that I can think of is that you have a custom error
handler somewhere in your code, which somehow does something unexpected
(exits the script execution or does something like an infinite recursion
which segfaults/OOMs your application.
if you still think that it isn't the case, then please open an issue on
bugs.php.net with a reproduce script, as this would be clearly a bug.



> Now if you are saying that I need to document these crashes as they SHOUL=
D
> not be happening then I'll roll things back and start doing that,


I would be generally surprised if you are serious about not knowing about
that triggering an E_STRICT shouldn't blow up your php.


> but *I* thought that these crashes were simply a known effect of using
> E_STRICT?


nope.
E_STRICT is currently the least serious/grave notice that the we have in
php(see the initial documentation at
http://php.net/manual/en/migrating5.errorrep.php), and until 5.4, it wasn't
part of E_ALL at all (see http://www.php.net/manual/en/migration54.other.ph=
p
 ).
which made some people bashing the project, that we call something E_ALL
which doesn't include everything.
so it was changed with 5.4, so


> And so I followed the directions, and switched E_STRICT off. On productio=
n
> machines of PHP5.3 with E_STRICT enabled and on PHP5.4 one gets white
> screen crashes using older code ... as far as I was concerned that was a
> known fact. Switch it off and everything runs fine!
>
>
would be nice if you could come up with a small snippet/stand alone script
to reproduce the issue and attach it to a bugreport.




--=20
Ferenc Kov=C3=A1cs
@Tyr43l - http://tyrael.hu

--047d7b2e09d7365e8004c8e0726d--