Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:86341 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 63601 invoked from network); 21 May 2015 11:45:03 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 21 May 2015 11:45:03 -0000 Received: from [127.0.0.1] ([127.0.0.1:24633]) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ECSTREAM id 2F/81-52687-F35CD555 for ; Thu, 21 May 2015 07:45:03 -0400 Authentication-Results: pb1.pair.com smtp.mail=flaupretre@free.fr; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=flaupretre@free.fr; sender-id=unknown Received-SPF: error (pb1.pair.com: domain free.fr from 212.27.42.3 cause and error) X-PHP-List-Original-Sender: flaupretre@free.fr X-Host-Fingerprint: 212.27.42.3 smtp3-g21.free.fr Received: from [212.27.42.3] ([212.27.42.3:35864] helo=smtp3-g21.free.fr) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 9D/51-52687-002CD555 for ; Thu, 21 May 2015 07:31:12 -0400 Received: from zimbra71-e12.priv.proxad.net (unknown [172.20.243.221]) by smtp3-g21.free.fr (Postfix) with ESMTP id 02059A62C0; Thu, 21 May 2015 13:29:59 +0200 (CEST) Date: Thu, 21 May 2015 13:31:09 +0200 (CEST) To: Nikita Popov Cc: PHP internals Message-ID: <1728446955.140561.1432207869694.JavaMail.root@zimbra71-e12.priv.proxad.net> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Originating-IP: [82.232.41.54] X-Mailer: Zimbra 7.2.0-GA2598 (ZimbraWebClient - FF3.0 (Win)/7.2.0-GA2598) X-Authenticated-User: flaupretre@free.fr Subject: Re: [PHP-DEV] Soft-reserve "void" class name From: flaupretre@free.fr References: Hi, > De: "Nikita Popov" > > For PHP 7 we soft-reserved a number of class names [1] like "numeric", so > that we have the ability to introduce them as typehints in a 7.x release. > "Soft" here means that we only document these names as being reserved and > don't throw an error when they're used. > > I'd like to add "void" to this list, so we have the option to introduce a > void return type in PHP 7.x. I've seen some disagreement as to whether th= is > should be called "void" or "null" - this discussion should be held when a= n > RFC comes up, however we need to keep both options open until then. > (Currently only "null" is reserved.) May I repeat my arguments to have this reservations enforced by a warning m= essage ? 'Soft' reservation is easier but it is not enough. If we give a special meaning to one of thes= e names in a 7.x release, we will introduce a BC break, whatever the documentation states, because th= at's the definition of a BC break : software that works fine in 7.0 and does not work the same in 7.x. = Do we want to guarantee BC on minor versions ? If we don't enforce a check on reserved class names, IMO, = we can't. Once again, this is a short-term half-baked solution we'll pay later. PS: If you're OK, I am ready to implement the check. Regards Fran=C3=A7ois