Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:82261 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 12135 invoked from network); 9 Feb 2015 10:44:42 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 9 Feb 2015 10:44:42 -0000 Authentication-Results: pb1.pair.com smtp.mail=ajf@ajf.me; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=ajf@ajf.me; sender-id=pass Received-SPF: pass (pb1.pair.com: domain ajf.me designates 192.64.116.200 as permitted sender) X-PHP-List-Original-Sender: ajf@ajf.me X-Host-Fingerprint: 192.64.116.200 imap1-2.ox.privateemail.com Received: from [192.64.116.200] ([192.64.116.200:43820] helo=imap1-2.ox.privateemail.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 45/4C-50460-99F88D45 for ; Mon, 09 Feb 2015 05:44:42 -0500 Received: from localhost (localhost [127.0.0.1]) by mail.privateemail.com (Postfix) with ESMTP id D344CB0008E; Mon, 9 Feb 2015 05:44:38 -0500 (EST) X-Virus-Scanned: Debian amavisd-new at imap1.ox.privateemail.com Received: from mail.privateemail.com ([127.0.0.1]) by localhost (imap1.ox.privateemail.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id YO3C9BMyT92i; Mon, 9 Feb 2015 05:44:38 -0500 (EST) Received: from [137.50.28.190] (oa-res-28-190.wireless.abdn.ac.uk [137.50.28.190]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.privateemail.com (Postfix) with ESMTPSA id 4EF6BB0008B; Mon, 9 Feb 2015 05:44:37 -0500 (EST) References: <8703B53E-2C4A-4AC6-95C4-D4F19C6D5221@ajf.me> <54D5659D.5000602@php.net> <54D7A6DB.3050209@seld.be> <74136F1E-817F-4A33-8228-B47045DD65C3@ajf.me> <54D7EB44.9010005@gmail.com> <54D7F972.4010107@seld.be> <2013B2A4-74E6-4452-8A48-E749DCBEA2EF@zend.com> Mime-Version: 1.0 (1.0) In-Reply-To: <2013B2A4-74E6-4452-8A48-E749DCBEA2EF@zend.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Message-ID: <6C020C7F-85C0-4C88-8766-48CEDA6290F8@ajf.me> Cc: Jordi Boggiano , "internals@lists.php.net" X-Mailer: iPhone Mail (12B466) Date: Mon, 9 Feb 2015 10:44:28 +0000 To: Zeev Suraski Subject: Re: [PHP-DEV] [VOTE] Scalar Type Hints From: ajf@ajf.me (Andrea Faulds) Hi, > On 9 Feb 2015, at 03:48, Zeev Suraski wrote: >=20 > A - has pretty much everybody agreeing with is a good idea. Nobody object= s to it. It's under consensus. This isn't true. I've explained why it isn't true several times. Maybe you a= re suffering from confirmation bias or something, but there is no such "cons= ensus". Quite a few internals contributors liked v0.1. Quite a few didn't. I= 've gone and evidenced this before in replies sent directly to you.=20 In addition, the reaction from the wider community was largely negative. > B - has a large number of people thinking it's alien to PHP, and has many p= eople objecting to it. B also has a large number of supporters because it is a pragmatic compromise= . A also had a large number of detractors. > The vote is on A+B. No it isn't. You are claiming, as I understand it, that: * Weak typing has consensus (it doesn't) * Strict typing is entirely controversial (it has many supporters, however) * This proposal including both somehow nullifies the argument that weak typi= ng lacks consensus (it doesn't - someone is free to oppose the addition of s= omething in isolation yet support its addition in combination) The truth of the matter is this. There are at least two approaches to scalar= type hint behaviour: weak and strict. Both are highly controversial. The ad= dition of either exclusively, is controversial. The addition of both togethe= r, is controversial. The addition of "stricter" weak typing, is controversia= l. The issue of scalar type hints is highly controversial in general for the= se reasons. There is no consensus whatsoever. To suggest there is would be to grossly ex= aggerate. -- Andrea Faulds http://ajf.me/=