Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:83087
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: unknown (pb1.pair.com: domain php.net does not designate 212.27.42.2 as permitted sender)
Reply-To: <francois@php.net>
To: "'Leigh'" <leight@gmail.com>,
	"'Sara Golemon'" <pollita@php.net>
Cc: "'PHP internals'" <internals@lists.php.net>
References: <CAESVnVoZYiMWQk1Ydc-9wbkJo7Ru_4mrUtrubW=Rh=QKK9o8TA@mail.gmail.com> <CAPwsocFUF9WcTxc-BjmaCccdPbeYs5VgyDvqYbx=3cR-SwoPkg@mail.gmail.com>
In-Reply-To: <CAPwsocFUF9WcTxc-BjmaCccdPbeYs5VgyDvqYbx=3cR-SwoPkg@mail.gmail.com>
Date: Wed, 18 Feb 2015 16:47:08 +0100
Message-ID: <032f01d04b92$2722e0d0$7568a270$@php.net>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Thread-Index: AQKz6wpj8b81mnwJq1LfxWbU4ZJyQgFU2plEmySkzlA=
Content-Language: fr
Subject: RE: [PHP-DEV] Scalar Type Hints v0.4
From: francois@php.net (=?utf-8?Q?Fran=C3=A7ois_Laupretre?=)

> De : Leigh [mailto:leight@gmail.com]
>
> Can we keep a 0) of "reserve names for future use in-case of RFC
> failure" option.

Reserving names is only needed as long as we keep keywords sharing the =
same naming space as classes. This is a mistake from the past and, as =
long as we keep it, each new keyword is a pain. Reserving keywords in =
advance can only lead to reserving too few or too much. So, IMO, =
deprecating bare class names as hint is first. Then, we can reserve a =
limited set of keywords.

> How do you propose weak typing works with these? Does it only allow
> one of the union of types through (thus making it strict), or does it
> try and coerce to one if it can? Which one does it pick?

That's exactly the problem we need to solve before going the union type =
road. A limited set can be implemented now as new zpp types, but none =
that requires questionable conversion (while useful, we are not ready =
for 'int|float', for example).

Regards

Fran=C3=A7ois