Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:69853
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.219.49 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <526974AE.1050601@php.net>
References: <CAF+90c8OgW4Nonaz+HQn+gi4r+AdaEMXsTxCAhn=WO-+aQQsZQ@mail.gmail.com>
	<526974AE.1050601@php.net>
Date: Thu, 24 Oct 2013 21:40:28 +0200
Message-ID: <CAF+90c9aKWgGNVm0NqPtmM_1VjSDxZXDFGHo9ksjJhVH1EqQ7A@mail.gmail.com>
To: Joe Watkins <krakjoe@php.net>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=001a11c2de605a375b04e981ced4
Subject: Re: [RFC] Exceptions in the engine
From: nikita.ppv@gmail.com (Nikita Popov)

--001a11c2de605a375b04e981ced4
Content-Type: text/plain; charset=ISO-8859-1

On Thu, Oct 24, 2013 at 9:27 PM, Joe Watkins <krakjoe@php.net> wrote:

> I have to ask the question; why stop at half way ??
>
> A warning does absolutely nothing for the programmer, or their code, all
> it does is warn the client, who isn't very likely to even be in contact
> with the programmer, even less likely has access to their code.
>
> [...]
>
> This solution has existed for years, why do we shy away from it so much ??
> I've never heard a really good argument for the existence of warnings or
> notices at all.
>
> This is all said with the knowledge that some errors are truly fatal,
> there is no point to, or chance of, throwing an exception.
>
> +1 on the whole idea, however far we are able to take it ... the further
> the better in my opinion ...
>

Changing existing warnings to exceptions would be a (massive) compatibility
break. Changing fatal errors isn't (in first order approximation) because -
well, they are fatal, you can't really depend on their behavior unless you
are using them as a die-substitute or something ^^

As this RFC is aimed at the 5.x branch it needs to maintain BC to a
reasonable level, so changing warnings is really out of its scope. If you
want to change warnings to exceptions that should be a separate proposal
targeted at PHP 6. I'd prefer to keep it out of this thread.

Thanks,
Nikita

--001a11c2de605a375b04e981ced4--