Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:62445
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.210.170 as permitted sender)
MIME-Version: 1.0
Sender: nicolas.grekas@gmail.com
In-Reply-To: <3E3A531D90FC43B8B7E9CDD37F1EEE40@pc>
References: <CAH-PCH7874id459NTuMqL6pzL=feRtaWUAiPiSqPDa73tnFy9w@mail.gmail.com>
 <CAOWwgpk7VbQbuB7NPG6KR3P+63cmdP0npjr7VCHhwo+H3p7QJg@mail.gmail.com> <3E3A531D90FC43B8B7E9CDD37F1EEE40@pc>
Date: Fri, 24 Aug 2012 09:23:32 +0200
Message-ID: <CAOWwgp=nWjh3swdSbpHEXFixq5zO_2NBUyJYBXyWjwE66K3Y=A@mail.gmail.com>
To: Stan Vass <sv_forums@fmethod.com>
Cc: Ferenc Kovacs <tyra3l@gmail.com>, PHP Internals <internals@lists.php.net>, 
	Andrew Faulds <ajf@ajf.me>, Etienne Kneuss <colder@php.net>, Stas Malyshev <smalyshev@sugarcrm.com>
Content-Type: multipart/alternative; boundary=20cf303e9d92a3a86404c7fddb6a
Subject: Re: [PHP-DEV] Error handling brainstorming
From: nicolas.grekas+php@gmail.com (Nicolas Grekas)

--20cf303e9d92a3a86404c7fddb6a
Content-Type: text/plain; charset=ISO-8859-1

> **
> The overall mood seems to be that since PHP has an error handler, everyone
> is free to handle errors any way they want.
> 2) When everyone starts handling errors in their own way with error
> handlers, you can't reliably use third party code. You are in your own
> universe.
>

I think that's the main point that makes any change to the way PHP
currently handles errors difficult:

The current behavior is to continue the execution flow (except for fatal
errors of course) whereas an exception always breaks it. Throwing an
exception, either in a custom or in a new internal handler, introduces a
major portability + backward compatibility issue.

But do you think it could be possible to introduce a per script declaration
of the way it has been coded regarding error handling ?
We could imagine for example that any script that is coded assuming
exceptions instead of errors could be force to declare with a :

<?php declare(throw_errors=1); ?> or maybe : <?php
declare(throw_errors=E_WARNING | E_NOTICE /* | ...*/);



> 1) PHP Errors come with a severity code and a string message. You want to
> handle specific errors in a specific way? You better start writing giant
> regexes parsing the string messages.
>

This is a problem that could also be addressed with the current error
handling mechanism: that would require that any error comes with some
unique number for example. Is this possible? Independently of the exception
vs classical error discussion, that would be amazing.

Regards,
Nicolas

--20cf303e9d92a3a86404c7fddb6a--