Re: handling non-fatal compile-time errors
| From: | Nikita Popov | Date: | Sun, 29 Sep 2013 11:42:28 +0000 |
| Subject: | Re: handling non-fatal compile-time errors | ||
| References: | 1 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-69412@lists.php.net to get a copy of this message | ||
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