Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:82975 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 70502 invoked from network); 17 Feb 2015 15:49:09 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 17 Feb 2015 15:49:09 -0000 Authentication-Results: pb1.pair.com smtp.mail=francois@php.net; spf=unknown; sender-id=unknown Authentication-Results: pb1.pair.com header.from=francois@php.net; 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:4868] helo=smtp2-g21.free.fr) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id C9/B0-19463-5F263E45 for ; Tue, 17 Feb 2015 10:49:09 -0500 Received: from moorea (unknown [82.240.16.115]) by smtp2-g21.free.fr (Postfix) with ESMTP id A515F4B014A; Tue, 17 Feb 2015 16:48:49 +0100 (CET) Reply-To: To: "'Andrey Andreev'" , "'Zeev Suraski'" Cc: "'Sara Golemon'" , "'PHP internals'" References: <011801d04a07$83ab1c00$8b015400$@php.net> <016f01d04a3a$e9183220$bb489660$@php.net> <022801d04ab1$4a0c47d0$de24d770$@php.net> <1913e09d7f52541901d8574d2080a63f@mail.gmail.com> In-Reply-To: Date: Tue, 17 Feb 2015 16:49:04 +0100 Message-ID: <025b01d04ac9$420721f0$c61565d0$@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/xwHih9+6AanvcsEBj7eMCwEU0CpMAs0H7+gBDwGZjwJNu28fAWzN03+dH60IsA== Content-Language: fr X-Antivirus: avast! (VPS 150217-1, 17/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?=) > De : Andrey Andreev [mailto:narf@devilix.net] > > > If we still see that employing the strict(er) rules is very noisy = with > > internal functions, a more appropriate option may be introducing new > types > > into ZPP, that would correspond to the new rules we introduce in the > > userland type hints, and requiring extension authors to explicitly = move to > > them where they believe it's appropriate. That will allow extension = authors > > to make their choice regarding their APIs, similarly to the process = that > > will happen in userland. >=20 > And that brings us back to square one ... Expose only 1 tool to > userland, but then give two options to the much less-populated crowd > of extension developers. That doesn't make sense to me. I must say 'no'. That's completely different of dual-mode, as it was not = clear, but the types we would add to ZPP would be also available in = userland. The objective is to maintain a full consistency between userland, = internal funcs, and documentation. This is so true that we'll probably, in the future, introduce ZPP = supported specialized types, like path, to userland. I am also quite = sure that we'll add a set of strict types, for the few cases where zval = type *really* matters (like sorting and other 'special' stuff). But we are not intending to make it more complex than needed for a first = release. We all need to practice before identifying additional needs. Cheers Fran=C3=A7ois