Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:82884 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 28437 invoked from network); 16 Feb 2015 20:39:08 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 16 Feb 2015 20:39:08 -0000 Authentication-Results: pb1.pair.com header.from=francois@php.net; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=francois@php.net; spf=unknown; sender-id=unknown Received-SPF: unknown (pb1.pair.com: domain php.net does not designate 212.27.42.2 as permitted sender) X-PHP-List-Original-Sender: francois@php.net X-Host-Fingerprint: 212.27.42.2 smtp2-g21.free.fr Received: from [212.27.42.2] ([212.27.42.2:14072] helo=smtp2-g21.free.fr) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 4D/4E-36518-96552E45 for ; Mon, 16 Feb 2015 15:39:08 -0500 Received: from moorea (unknown [82.240.16.115]) by smtp2-g21.free.fr (Postfix) with ESMTP id 146484B0204; Mon, 16 Feb 2015 21:38:48 +0100 (CET) Reply-To: To: "'Levi Morrison'" Cc: "'Arvids Godjuks'" , "'Jefferson Gonzalez'" , "'Rowan Collins'" , "'PHP internals'" References: <011801d04a07$83ab1c00$8b015400$@php.net> In-Reply-To: Date: Mon, 16 Feb 2015 21:39:00 +0100 Message-ID: <015901d04a28$98b60f80$ca222e80$@php.net> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable X-Mailer: Microsoft Outlook 14.0 Thread-Index: AQGD0sLDaA+/0NIeBlQhQC5OtPA/xwJHumt0nXpsRSA= Content-Language: fr X-Antivirus: avast! (VPS 150216-0, 16/02/2015), Outbound message X-Antivirus-Status: Clean Subject: RE: [PHP-DEV] Reviving scalar type hints From: francois@php.net (=?utf-8?Q?Fran=C3=A7ois_Laupretre?=) Hi, > De : morrison.levi@gmail.com [mailto:morrison.levi@gmail.com] De la = part >=20 > Also, I know people REALLY want scalar types in PHP 7.0 but honestly > all we need to do is reserve the keywords so there is no BC impact and > then we can do it at any point during the PHP 7 lifecycle. This is my > preferred course of action, because right now this internals mailing > list is in HIGH STRESS MODE. I would rather just take the action of > reserving the types so it can be done in 7.1 (or 7.2 or even if it's > never, I would prefer to reserve these words). If we deprecate using bare class names as type hints and replace it with = the 'object(classname)' syntax, we can reserve keywords for 7.0 and, = maybe 7.1 but potential name clashes should be away in 7.2. Fran=C3=A7ois