Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:85103
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.214.172 as permitted sender)
MIME-Version: 1.0
Sender: yohgaki@gmail.com
In-Reply-To: <CAEZPtU7C3C14D9GwgY7QidaFC3CHjvc5fJY4CqnJU4jQaWD5WQ@mail.gmail.com>
References: <CAGa2bXaqxbSoy7SP0rnd5D4mKZCC1zDYJX8CvK_6DrA+zmo=oA@mail.gmail.com>
 <CAEZPtU7C3C14D9GwgY7QidaFC3CHjvc5fJY4CqnJU4jQaWD5WQ@mail.gmail.com>
Date: Tue, 17 Mar 2015 07:41:24 +0900
Message-ID: <CAGa2bXbOKXWGEM=_2_mZxiVK8bdjAYNH-nyOKmGQ=tddKvcDVA@mail.gmail.com>
To: Pierre Joye <pierre.php@gmail.com>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=001a1140b2322fafc805116f8f73
Subject: Re: [PHP-DEV] [RFC] Introduce Type Affinity
From: yohgaki@ohgaki.net (Yasuo Ohgaki)

--001a1140b2322fafc805116f8f73
Content-Type: text/plain; charset=UTF-8

Hi Pierre,

On Tue, Mar 17, 2015 at 7:23 AM, Pierre Joye <pierre.php@gmail.com> wrote:

> I very much appreciate your consistent effort to improve php, at all
> levels.
>
> However I won't comment on this RFC or any further RFCs trying to target
> 7.
>
> My reasoning is that we should now focus on getting it out, in time. I did
> not agree with the time plan about 7 development but it is what we decided.
> Let get back to work now.
>
I agree that we should concentrate for PHP7.0.
The reason why I raised this topic is currently proposed "strict_types"
does not work
well with this.

If inputs are converted/validated as certain types with or without this
RFC, "strict_types"
should raise error for mismatched types. However, current proposal does not
do this
depending on how "strict_types" is used...

Regards,

--
Yasuo Ohgaki
yohgaki@ohgaki.net

--001a1140b2322fafc805116f8f73--