Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:83089 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 77967 invoked from network); 18 Feb 2015 16:28:29 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 18 Feb 2015 16:28:29 -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:64017] helo=smtp2-g21.free.fr) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 21/04-56339-BADB4E45 for ; Wed, 18 Feb 2015 11:28:28 -0500 Received: from moorea (unknown [82.240.16.115]) by smtp2-g21.free.fr (Postfix) with ESMTP id 608074B02BE; Wed, 18 Feb 2015 17:28:04 +0100 (CET) Reply-To: To: =?utf-8?Q?'P=C3=A1draic_Brady'?= , "'Andrey Andreev'" Cc: "'Zeev Suraski'" , "'Nikita Popov'" , "'Rasmus Lerdorf'" , "'Sara Golemon'" , "'PHP internals'" References: <54E3E27B.2010903@lerdorf.com> <2f99c47df51fa6c73131032ec50fade0@mail.gmail.com> In-Reply-To: Date: Wed, 18 Feb 2015 17:28:21 +0100 Message-ID: <034d01d04b97$e9a3dec0$bceb9c40$@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: AQKz6wpj8b81mnwJq1LfxWbU4ZJyQgGjcksIAbrU1N8Bn0wufQGLyLi6AmixSwcCoM80eprSwCPQ Content-Language: fr X-Antivirus: avast! (VPS 150218-0, 18/02/2015), Outbound message X-Antivirus-Status: Clean Subject: RE: [PHP-DEV] Scalar Type Hints v0.4 From: francois@php.net (=?utf-8?Q?Fran=C3=A7ois_Laupretre?=) > De : P=C3=A1draic Brady [mailto:padraic.brady@gmail.com] > > However, =E2=80=9C123=E2=80=9D is exceptional. It=E2=80=99s redefining = an integer as =E2=80=9C an > integer or a string comprised wholly of digits without leading zeroes, > with an optional leading hyphen, and representing an integer up to > PHP_INT_MAX=E2=80=9D Add leading zeros, and leading/trailing blanks and I think it is still = strict enough. > Then again, it=E2=80=99s an exception that requires a long sentence. = It=E2=80=99s just > not clear, to me, if this is the sole intended exception, or if that > sentence needs to be expanded to a paragraph. A section? Are we going > to need a chapter? I=E2=80=99m assuming octals-in-a-string are a no-go = to be > coerced whereas others might just see an integer with superfluous > leading zeroes. Leading zeros to recognize octal string are not an option, but = alternative non ambiguous syntax is possible, in theory. '0x'-prefixed hexa is possible too. Thoughts ? > In a future RFC revision, it might be nice to have a table of the > specific coercion rules applicable to a weak/strong/single-unified > option. I am currently writing this. Regards Fran=C3=A7ois