Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:83320
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain kingsquare.nl designates 141.138.142.202 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CAPhkiZx0LBKze1XxiknEuOuwkPkCQdcR6Htnz=BdidxUKd-5XQ@mail.gmail.com>
References: <CAFMT4No-KBHn6s5MqTV9CAQYHKCMWbiOnAwfPx8Xj=-x5++hHg@mail.gmail.com>
 <CAFMT4NpTHMtfJuqO_RC6c8cv2Zg=JxFBC7pn6RHnrzqCON_r6Q@mail.gmail.com>
 <04db01d04cc1$d9925770$8cb70650$@php.net> <CAPhkiZyH1erPE=Set9dOdtv=ikOB64u1NLnsn12dm5qPcxPOLQ@mail.gmail.com>
 <CAFMT4NprvaGUV2mHkLf9ZyXm7WBmX4r-shy9vZXyhymMeT5YJw@mail.gmail.com> <CAPhkiZx0LBKze1XxiknEuOuwkPkCQdcR6Htnz=BdidxUKd-5XQ@mail.gmail.com>
Date: Fri, 20 Feb 2015 17:24:54 +0100
Message-ID: <CADq_CxooEoUri4unvtYHC=8AXe9kMDyVAU6LPPjFt5JBM9dJtQ@mail.gmail.com>
To: internals <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Subject: Re: [PHP-DEV] Re: [RFC] Reserving More Types in PHP 7
From: robin@kingsquare.nl ("Kingsquare.nl - Robin Speekenbrink")

Hi,

First of all I'd like to see this (clean) RFC formalized / ratified
sooner rather than later.

Just to chime in here from a user / framework developer perspective in
regards to *double* / *real* / *boolean* / *integer* reservation: i'd
like to see these aliases (and the is_*-functions etc) be deprecated /
removed sooner than later instead of kept around. It's minor, i know,
but consistency wins above a quick find/replace above all. With lesser
roads to the destination (rome), the easier the route to follow ;)

Atleast have it on a roadmap somewhere instead of keeping it around
and in every discussion with regards to reserved keywords, typehints,
return types etc etc

Thanks and keep up the good work ! (can't wait to see what PHP7.0 will
actually bring to the table)

Thnx,

Robin Speekenbrink


2015-02-20 17:11 GMT+01:00 Andrey Andreev <narf@devilix.net>:
> Hi,
>
> On Fri, Feb 20, 2015 at 6:00 PM, Levi Morrison <levim@php.net> wrote:
>> On Fri, Feb 20, 2015 at 4:21 AM, Andrey Andreev <narf@devilix.net> wrote:
>>>
>>> Agree on 'double' though ... if we want to discourage its usage, we
>>> might even think of deprecating it.
>>
>> While deprecating it might be a good course of action, it is out of
>> scope of this RFC. I personally think that reserving it is a good way
>> to discourage its use: simply reserve it and then don't use it for
>> anything. If we decide not to use the aliases if we have scalar types
>> and the aliases are reserved this would prevent users from making
>> custom types from the aliases. In my opinion this a Good Thing.
>
> Well, I meant to deprecate is_double(), is_real() and the
> corresponding explicit casts. I might be missing other places when
> they are used, not sure, but the point would be to stop using these
> names for scalar types at all, so that everybody can freely use them
> for class/trait/interface names ... I don't think anybody would do
> that only for pseudo-scalar hinting objects.
>
> So, while yes - that's outside of this RFC's scope, reserving them as
> keywords would be the opposite of what I had in mind.
>
> Cheers,
> Andrey.
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>