Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:80165
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.170 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <E0607EA7-8B88-453B-8C57-B3F3D32DEE80@ajf.me>
References: <41D5BB0B-73AF-488E-968D-90B2878E3178@ajf.me> <54A466CB.9020400@gmail.com>
 <alpine.DEB.2.11.1501041727320.4080@whisky.home.derickrethans.nl>
 <54A9D39F.8010808@gmail.com> <E0607EA7-8B88-453B-8C57-B3F3D32DEE80@ajf.me>
Date: Mon, 5 Jan 2015 01:53:39 +0100
Message-ID: <CADyq6sKfRKi_1bc=BXJLFdTj5jU=xrx1iOd3c3pT_8jcX924AQ@mail.gmail.com>
To: Andrea Faulds <ajf@ajf.me>
Cc: Stanislav Malyshev <smalyshev@gmail.com>, Derick Rethans <derick@php.net>, 
	PHP Internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=047d7beb9c8c4dcde0050bdd20c8
Subject: Re: [PHP-DEV] [RFC] Scalar Type Hints
From: ocramius@gmail.com (Marco Pivetta)

--047d7beb9c8c4dcde0050bdd20c8
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On 5 January 2015 at 01:07, Andrea Faulds <ajf@ajf.me> wrote:

> Hi Stas,
>
> > On 4 Jan 2015, at 23:58, Stanislav Malyshev <smalyshev@gmail.com> wrote=
:
> >
> >> I think it's perfectly acceptable that PHP makes a built-in type a
> >> reserved word. I would certainly not change it to PHPInt to "avoid any
> >> obvious clashes".
> >
> > As I already pointed out, if we make it reserved word we'll have BC
> > problem. We already had this experience when goto became reserved word =
-
> > it resulted in a lot of breakage. This would be bigger, since we adding
> > more reserved words and we know they are used in a lot of class names
> > (and, possibly, method names too).
>
> It is a BC problem, yes. However, it can be worked around in userland in =
a
> way where unchanged code will continue to work on PHP 5, and changed code
> will work on both PHP 5 and PHP 7. I think the BC break is worth it, thou=
gh
> unfortunate. I also wonder why we hadn=E2=80=99t reserved these names bef=
ore, it
> seems rather silly that you were ever able to make a class called =E2=80=
=9Cinteger=E2=80=9D
> or =E2=80=9Carray=E2=80=9D.


Note that this kind of BC break will gladly be fixed in major libraries out
there: we can rename those classes and announce the breakages ourselves
without too many problems.

The best way to eagerly detect this sort of problem would be to have a
php-nightly version on travis-ci, and then we could handle it ourselves and
without too much pain (already trying to get there, and mbeccati has a CI
system running with php7 and some major libs).

The only trouble that could eventually come up is with legacy software that
isn't tested at all.

Marco Pivetta

http://twitter.com/Ocramius

http://ocramius.github.com/

--047d7beb9c8c4dcde0050bdd20c8--