Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:68443
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.223.169 as permitted sender)
MIME-Version: 1.0
Date: Thu, 8 Aug 2013 17:11:37 +0200
Message-ID: <CAH-PCH7-oZT7u0KB7bbDFNmZGeMiSUcU0-Shsp7rXmwaOb3muA@mail.gmail.com>
To: PHP Internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=089e011821ea0cfd0104e3711340
Subject: handling non-fatal compile-time errors
From: tyra3l@gmail.com (Ferenc Kovacs)

--089e011821ea0cfd0104e3711340
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi,

I've just bumped into https://bugs.php.net/bug.php?id=3D65322 recently, and=
 I
would like you get some opinions on the issue.
Personally I think that it is a really bad design to introduce
pedantic(E_STRICT) errors which can break basic functionality of the engine
(calling the registered autoloader), so if there is no viable solution to
make the autoloader work for these kind of errors, I would like to propose
removing the offending errors and make it a rule to not add compile-time
non-fatal errors until the problem is resolved.

ps: on a related note, somehow I got the feeling that Lester complaining
that E_STRICT errors fataling/crashing the application migrated to PHP 5.4
was related to this problem, and I'm a bit sad that we didn't managed to
figure this out back then.

--=20
Ferenc Kov=C3=A1cs
@Tyr43l - http://tyrael.hu

--089e011821ea0cfd0104e3711340--