Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:86385
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.212.181 as permitted sender)
Message-ID: <556363D3.1040902@gmail.com>
Date: Mon, 25 May 2015 19:02:59 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0
MIME-Version: 1.0
To: internals@lists.php.net
References: <971AB39D-1E20-43E8-9CF1-A7F67E3C14C3@icicle.io> <CAGa2bXb8CaJsJorx0HTzSgEeAGXJN7DoW5vi=m+wFiUXNw+tng@mail.gmail.com>
In-Reply-To: <CAGa2bXb8CaJsJorx0HTzSgEeAGXJN7DoW5vi=m+wFiUXNw+tng@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] [RFC] Throwable Interface
From: rowan.collins@gmail.com (Rowan Collins)

On 24/05/2015 22:32, Yasuo Ohgaki wrote:
> Does this include internal function type errors?
> e.g.
>
> $ php -r 'var_dump(mt_srand("99999999999999999999999999999999999"));'
> PHP Warning:  mt_srand() expects parameter 1 to be integer, string given in
> Command line code on line 1
> NULL
>
> If not, please make these exceptions rather than E_WARNING.
> We need consistency here.

Changing a Warning to an Exception is a much bigger deal than changing 
an Error to an Exception. While an Exception *can* be caught, the 
fundamental nature of it is that it is *fatal* if it is not caught. So 
you would be changing an advisory warning to a fatal error.

There might be cases where this would be sensible, but this has nothing 
to do with a) changing Errors to Exceptions (which has already passed) 
or b) changing the hierarchy to add a Throwable interface (the subject 
of this thread).

Regards,

-- 
Rowan Collins
[IMSoP]