Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:84564
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain basereality.com from 209.85.160.181 cause and error)
MIME-Version: 1.0
In-Reply-To: <8cdd5272816cf2b22ea9793d80ba5074@mail.gmail.com>
References: <ff8e8d5564b00b7baead3d9dd46282c8@mail.gmail.com>
	<CA+kxMuTg6kpX4oTVfJQbBRQB5RyuJbH5qLJOrrj098sDRW4Geg@mail.gmail.com>
	<8cdd5272816cf2b22ea9793d80ba5074@mail.gmail.com>
Date: Wed, 11 Mar 2015 18:03:55 +0000
Message-ID: <CA+kxMuRYsmu=Twdt0GorObL--11GO0iZwiMSpsr8oQObWsv_oA@mail.gmail.com>
To: Zeev Suraski <zeev@zend.com>
Cc: PHP internals <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Subject: Re: [PHP-DEV] [VOTE][RFC] Coercive Scalar Type Hints
From: danack@basereality.com (Dan Ackroyd)

On 11 March 2015 at 16:45, Zeev Suraski <zeev@zend.com> wrote:
> I think that going through a transition period ... that ultimately results
> in one, consistent language behavior

This RFC is explicitly saying that there is stuff that will be need to
be changed in the future. Why would anyone upgrade from PHP 5.6 to PHP
70 when there are going to be more changes to the type system?

Everyone would wait until that future version of PHP to upgrade and so
just have to do a single migration, instead of having to do two
migrations?

This is clearly worse than the strict STH RFC; with that people can
write code that will work on 5.x, 7 and 7.x by just not using scalar
type hints.

cheers
Dan