On Feb 20, 2015 8:11 AM, "Andrey Andreev" <n...@devilix.net> wrote: > > Hi, > > On Fri, Feb 20, 2015 at 6:00 PM, Levi Morrison <le...@php.net> wrote: > > On Fri, Feb 20, 2015 at 4:21 AM, Andrey Andreev <n...@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.
Right, but it is a yes/no list of options. It makes no sense to have competitive RFCs for such a trivial set of choices. > Cheers, > Andrey. > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php >
