Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:82615 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 24319 invoked from network); 13 Feb 2015 14:30:59 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 13 Feb 2015 14:30:59 -0000 Authentication-Results: pb1.pair.com header.from=patrickallaert@php.net; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=patrick.allaert@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.177 as permitted sender) X-PHP-List-Original-Sender: patrick.allaert@gmail.com X-Host-Fingerprint: 74.125.82.177 mail-we0-f177.google.com Received: from [74.125.82.177] ([74.125.82.177:57482] helo=mail-we0-f177.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id AB/20-22763-1AA0ED45 for ; Fri, 13 Feb 2015 09:30:58 -0500 Received: by mail-we0-f177.google.com with SMTP id m14so11086894wev.8 for ; Fri, 13 Feb 2015 06:30:53 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=mime-version:references:from:date:message-id:subject:to:cc :content-type; bh=efQk+xKMA2WsCl3CSi38lMt3LaTpMKru2wh4GpMVUOo=; b=CZmWrYM8a5pmLX8IoAIc7wJllfRQUDYQn+UnP8/k6pWIdSZ3KGegYsBoR1UM5wxcln B0p9ujo298lUir+JuzAHtT7lW6vNdrHlwxTS+P4FnCcxlfiziEc9yla7GM50iC9zDGhk qYesanQ/RFhp/r+2EBkL1DzwbDqTHErN0cELAFIC4z3ufPdiEOD80rA17ODhVcVZhMnW OJni6X5JbxdDCuLqEvmMy7PrPYNoEljzSx3dW3harcPQ2b8T9nPfzjRVsEe7W+IjXDPe dSk3jt9ZbjP47z7TeQcDLOAl+eyVQwORbnbuT2pRS/RydE8xCVsTSBnwxSjd5O4R0fH0 X0WQ== X-Received: by 10.194.210.103 with SMTP id mt7mr19047717wjc.103.1423837382505; Fri, 13 Feb 2015 06:23:02 -0800 (PST) MIME-Version: 1.0 References: <93453174-E6A8-47C6-8AB6-A08858A7FC05@zend.com> Date: Fri, 13 Feb 2015 14:23:02 +0000 Message-ID: To: Zeev Suraski , Andrea Faulds Cc: PHP Internals Content-Type: multipart/alternative; boundary=001a1133625466fd23050ef8f9da Subject: Re: [PHP-DEV] [VOTE] Scalar Type Hints From: patrickallaert@php.net (Patrick ALLAERT) --001a1133625466fd23050ef8f9da Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Le Fri Feb 13 2015 at 12:34:29, Zeev Suraski a =C3=A9crit : > > On 13 =D7=91=D7=A4=D7=91=D7=A8=D7=B3 2015, at 13:13, Andrea Faulds wrote: > > Hi, > > On 13 Feb 2015, at 09:37, Patrick ALLAERT wrote: > > > Voted "no" because of the reasons already mentioned by a bunch of others > here. > > > Weak type hint as presented earlier: +1 (and very good job Andrea about > that!). > > declare(strict_types=3D1): -1, not only about the syntax, but also about = the > mixed mode it introduces. > > > I'm pretty confident that this RFC will "pass" with just above 2/3 of > majority while it could reach much more. > > > I am pretty sure that if this RFC doesn't include a strict type mode _the > way it is proposed_ (or even, not at all, as part of another related RFC)= , > it would have some "no" converted to "yes" and would have a wider adoptio= n, > which is for sure a better option than relying on a voting mechanism whic= h > still is a supporting tool, we're not politicians after all :) > > > It wouldn=E2=80=99t have wider adoption. Excluding a large portion of the= PHP > community (which favours strict types) and giving them something which > doesn=E2=80=99t work for their use cases (weak types) is not going to win= any fans. > > > Any fans? Really? > > How about we put it to a test instead of guessing the outcome? > I'm wondering who would change their vote from "no" to "yes" if we consider a related, but separate, RFC for handling types in a more "strict" way. I most probably would! I guess (I don't pretend being in everyone's head), that few would do the opposite: changing their "yes" to "no" because of that. That is a lot of "guess" (whatever the sides) and measuring the opinions would be more appropriate IMHO. Cheers and have a nice WE everyone! Patrick --001a1133625466fd23050ef8f9da--