Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:53912
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.83.42 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CACwt+Jc=yGjr_YQ-i_gDs5DyUhGajTHxa5hJ1g4qfEWDyhvBaw@mail.gmail.com>
References: <CACwt+Jc=yGjr_YQ-i_gDs5DyUhGajTHxa5hJ1g4qfEWDyhvBaw@mail.gmail.com>
Date: Tue, 12 Jul 2011 11:09:33 +0200
Message-ID: <CAEZPtU6G3W--vncmu4qJ5V8fERkad+6O5S-n+g+jgcyNJNeubg@mail.gmail.com>
To: Patrick ALLAERT <patrickallaert@php.net>
Cc: Stas Malyshev <smalyshev@sugarcrm.com>, PHP Internals <internals@lists.php.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] Make primitive type names reserved words (Was: Re:
 [PHP-DEV] [RFC] 5.4 features for vote (long))
From: pierre.php@gmail.com (Pierre Joye)

hi,

As of now I do not think we should allow this change, whether the RFC
is accepted or not does not matter as it will badly break BC. Unless
there is a patch allowing this change without affecting existing code
(main point being namespaced code working smoothly), this RFC should
be rejected.

Cheers,

On Sun, Jul 10, 2011 at 6:41 PM, Patrick ALLAERT <patrickallaert@php.net> w=
rote:
> 2011/6/17 Stas Malyshev <smalyshev@sugarcrm.com>:
>
> [snip]
>
>> 2. Make primitive type names reserved words (in case we ever want some f=
orm
>> of scalar typing or anything else with scalar types). Using them as
>> identifiers would return parse error for now. May have BC implications.
>
> I am not sure it is a good idea to make them reserved words without a
> clear reason for doing so.
>
> I'm sure some projects have defined classes with those keywords in
> some namespace (to ensure they wouldn't conflict with possible PHP
> built-in stuff) like in:
>
> namespace \Types {
> =A0 =A0class Int {
> =A0 =A0 =A0 =A0// ...
> =A0 =A0}
> =A0 =A0class Float {
> =A0 =A0 =A0 =A0// ...
> =A0 =A0}
> =A0 =A0class String {
> =A0 =A0 =A0 =A0// ...
> =A0 =A0}
> =A0 =A0// ...
> }
>
> Developer may have taken care of defining them in a specific
> namespace, would it be possible to not break their application while
> making them reserved keywords in the global namespace only?
>
> I would be +1 if this could be done for the global namespace only.
> However, -1 if this would break the usage of classes like \Types\Int,
> \Types\String, ... would break.
>
> Please, rethink your vote taking this into account. I don't think it
> is required to hurry up on that decision while we still don't have a
> *clear* proposition for scalar type hinting.
>
> Cheers,
> Patrick
>
> [snip]
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>



--=20
Pierre

@pierrejoye | http://blog.thepimp.net | http://www.libgd.org