Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:69412
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.212.43 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CAH-PCH7-oZT7u0KB7bbDFNmZGeMiSUcU0-Shsp7rXmwaOb3muA@mail.gmail.com>
References: <CAH-PCH7-oZT7u0KB7bbDFNmZGeMiSUcU0-Shsp7rXmwaOb3muA@mail.gmail.com>
Date: Sun, 29 Sep 2013 13:42:28 +0200
Message-ID: <CAF+90c-sPCfbgViqrgAoMCE_EeKowYa8TaKku6vyOT8zpBHRiw@mail.gmail.com>
To: Ferenc Kovacs <tyra3l@gmail.com>
Cc: PHP Internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=089e0149ca3ad43cf004e7843605
Subject: Re: [PHP-DEV] handling non-fatal compile-time errors
From: nikita.ppv@gmail.com (Nikita Popov)

--089e0149ca3ad43cf004e7843605
Content-Type: text/plain; charset=ISO-8859-1

On Thu, Aug 8, 2013 at 5:11 PM, Ferenc Kovacs <tyra3l@gmail.com> wrote:

> Hi,
>
> I've just bumped into https://bugs.php.net/bug.php?id=65322 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.
>

I didn't look into the underlying problem with the autoloader, but just
removing the errors is not a solution. If this is so problematic we should
just drop E_STRICT and use more appropriate error types that already exist
- e.g. in the compiler E_COMPILE_WARNING can be used, which will not invoke
a custom error handler and as such can't cause this issue. We already have
special error types for the compiler, so why not use them?

Nikita

--089e0149ca3ad43cf004e7843605--