Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:85962
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain beberlei.de from 74.125.82.49 cause and error)
MIME-Version: 1.0
In-Reply-To: <553DBEC4.7000609@gmail.com>
References: <EC598AEEF641411B949D685DF8262B4E@gmail.com>
	<CAFMT4Npcjz9kQjfSrKH3JwoyEUqCE6DzWnAaZ5c_idcuVAQ2fA@mail.gmail.com>
	<A326B86EEE4C4E36B85455E01F355A22@gmail.com>
	<553DBEC4.7000609@gmail.com>
Date: Mon, 27 Apr 2015 10:15:19 +0200
Message-ID: <CAEPJdu=ofsYZ9PnU3r7kEnm_kX+RV+iTjsGsKRBaJSgpjpAsYw@mail.gmail.com>
To: Stanislav Malyshev <smalyshev@gmail.com>
Cc: Nate Abele <nate.abele@gmail.com>, internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=f46d04428e3ec018a60514b05879
Subject: Re: [PHP-DEV] Re: [RFC] Reserving More Types in PHP 7
From: kontakt@beberlei.de (Benjamin Eberlei)

--f46d04428e3ec018a60514b05879
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Mon, Apr 27, 2015 at 6:44 AM, Stanislav Malyshev <smalyshev@gmail.com>
wrote:

> Hi!
>
> > Well, it looks to me like all the discussion is around preventing
> > class and namespace names like =E2=80=9Cstring=E2=80=9D, =E2=80=9Cfloat=
=E2=80=9D, etc. Granted, PHP
> > class names are case-insensitive, but how hard would it be to reserve
> > these in a case-sensitive way?
>
> With current engine - I'd say it is hard. We can't really say "class
> names are case insentitive unless it's "string" or "float" or "boolean"
> in which case they are case sensitive". Imagine how code implementing
> such logic would look like, not to talk about the inconsistencies...
>
> > Lithium, CakePHP, and Drupal all have String classes. These aren=E2=80=
=99t
>
> Unfortunately, with scalar types we don't have much choice. I don't see
> how scalar types and classes named "string" can coexist.
>
> > I get that PHP 7 is the big opportunity to break backward
> > compatibility, but yeesh, really? It=E2=80=99s like we=E2=80=99re not e=
ven trying
> > anymore.
>
> There was a lot of discussion about this topic. Right now, unless
> there's a proposal to fix it that works, I don't see what can be done
> about it.
>

It should be possible to write something with PHP Parser detecting all the
occurances of "String/string" class usage to at least give a worklog of
entries that need to be changed, or maybe generate a patch file that can be
applied to the code base after review.


> --
> Stas Malyshev
> smalyshev@gmail.com
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>

--f46d04428e3ec018a60514b05879--