Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:80115
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.216.179 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <54A778AB.6020804@gmail.com>
References: <41D5BB0B-73AF-488E-968D-90B2878E3178@ajf.me>
	<CAEZPtU79=VX1Scm6vVn-9iuHD=qqRoPMrsR4Ymqd9=QQeQbRCg@mail.gmail.com>
	<54A778AB.6020804@gmail.com>
Date: Fri, 2 Jan 2015 21:33:32 -0800
Message-ID: <CAEZPtU6PtfRvxykJup4L=n52WAevf2cZ6q5ZmCqYmiSTzO3Aqw@mail.gmail.com>
To: Stanislav Malyshev <smalyshev@gmail.com>
Cc: Andrea Faulds <ajf@ajf.me>, PHP Internals <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Subject: Re: [PHP-DEV] [RFC] Scalar Type Hints
From: pierre.php@gmail.com (Pierre Joye)

On Fri, Jan 2, 2015 at 9:05 PM, Stanislav Malyshev <smalyshev@gmail.com> wrote:
> Hi!
>
>> I am also not a fan of errors, exception, at least for methods, make
>> much more sense. I know it is relatively easy to handle errors as
>> exception but still, let do it right now.
>
> Then we need to convert all parameter mismatch errors (or at least all
> fatal ones) to exceptions. Which I don't think makes a lot of sense to
> put in the same RFC but in any case it should work the same way over all
> the engine. Otherwise handling it would be a nightmare.

I am not sure about that. Parameters handling is one specific case,
userland parameter handling even more. It could be a good move to do
that as a 1st step, with this RFC.


-- 
Pierre

@pierrejoye | http://www.libgd.org