Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:86082
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: "'Christoph Becker'" <cmbecker69@gmx.de>,
	"'PHP internals'" <internals@lists.php.net>
Cc: <nikic@php.net>
References: <55415E10.7040908@gmx.de>
In-Reply-To: <55415E10.7040908@gmx.de>
Date: Thu, 30 Apr 2015 11:03:40 +0200
Message-ID: <016501d08324$8d300460$a7900d20$@php.net>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Thread-Index: AQGUoKRhP1A7Uprtq44CppZWICgrU53dBK5w
Content-Language: fr
Subject: RE: [PHP-DEV] Reserve even more type hints RFC
From: francois@php.net (=?utf-8?Q?Fran=C3=A7ois_Laupretre?=)

> De : Christoph Becker [mailto:cmbecker69@gmx.de]
>=20
> Relying on documentation only seems to be insufficient to me.  =
Consider
> a developer not reading the documentation and facing the issue that
> his/her code might break with PHP 7.1 (i.e. a minor version).

+1. I already asked if we should enforce reserved names by a message and =
most replied that documentation was enough. This is the lazy (I could =
say 'political') option and can only lead to bad surprises when we =
decide to use the names. At this time, saying "People should have read =
the doc" won't help them in any way, especially if their code dates back =
from before 7.0, when this doc didn't exist yet.

We don't need a warning there, we need a fatal error. These names are =
*invalid* as class names.

Regards

Fran=C3=A7ois