Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:82177 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 57021 invoked from network); 8 Feb 2015 21:22:29 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 8 Feb 2015 21:22:29 -0000 Authentication-Results: pb1.pair.com smtp.mail=zeev@zend.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=zeev@zend.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain zend.com designates 209.85.213.169 as permitted sender) X-PHP-List-Original-Sender: zeev@zend.com X-Host-Fingerprint: 209.85.213.169 mail-ig0-f169.google.com Received: from [209.85.213.169] ([209.85.213.169:43205] helo=mail-ig0-f169.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 54/E5-26926-493D7D45 for ; Sun, 08 Feb 2015 16:22:29 -0500 Received: by mail-ig0-f169.google.com with SMTP id hl2so11971235igb.0 for ; Sun, 08 Feb 2015 13:22:26 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:references:in-reply-to:mime-version :thread-index:date:message-id:subject:to:cc:content-type; bh=PQglvyBk28C93FBIdPA7fJxNsU/Zfs58OD3HaUntvSg=; b=k05yMt7Rv3TQrIpeUQ+pLEBWfqOdhg6d7zVZPWwPxsmFentHC1h9r0R+dpjJ6BVGb4 +9o2d6MKarZiZtwl7NDkQfaLROGknVIJvuCFKnFObqHBpFmp2qvTx/zZ7/djZCzLImt4 27ecNdTEOb6Apc9s51r+gSuMvYv7aZrjvEkSejUWrZeMfx4feUWfIC1AsXuRehP+FQ0R GvN7zwNRHE1U9NCjF6RfyxEB2UK97fudc1qVPMBYnt4FuvCuwtAosUeNg2lAYdYnNJL/ BR98qNSYReo1vf7y0AhOf9Z2n6aAdysXdKNrA3SbQW5hjFpvlbGXi0SCw6NEtH5bhb9S hEFQ== X-Gm-Message-State: ALoCoQm+O00P1347e3ZiijdcX/k03cENu8NjEIRpgBc2TcwMJAgo0obMsXZPnqQPT0EqoSxoGmF5rcf0hAeE9ZNzHwD69pXnl3TK9J46N1r8SeG6lJ/k2jq9IO4QC2mpiZLsRcowPpY+8mDzDrVlG7EqvkY7oCTCTA== X-Received: by 10.42.211.200 with SMTP id gp8mr8086740icb.93.1423430545942; Sun, 08 Feb 2015 13:22:25 -0800 (PST) References: <8703B53E-2C4A-4AC6-95C4-D4F19C6D5221@ajf.me> <54D5659D.5000602@php.net> <54D7A6DB.3050209@seld.be> In-Reply-To: MIME-Version: 1.0 X-Mailer: Microsoft Outlook 14.0 thread-index: AQJMIZG9mXkdirFXmuP9r5ZK3xIuzQGYx3GRAvm0W3gBWDJV2AHmZti9Ad7HVqibogel4A== Date: Sun, 8 Feb 2015 23:22:25 +0200 Message-ID: <0a344270616df2c33c8a1f5db2df08a0@mail.gmail.com> To: Matthew Leverton Cc: PHP internals Content-Type: text/plain; charset=UTF-8 Subject: RE: [PHP-DEV] [VOTE] Scalar Type Hints From: zeev@zend.com (Zeev Suraski) > -----Original Message----- > From: Matthew Leverton [mailto:leverton@gmail.com] > Sent: Sunday, February 08, 2015 11:17 PM > To: Zeev Suraski > Cc: Jordi Boggiano; PHP internals > Subject: Re: [PHP-DEV] [VOTE] Scalar Type Hints > > On Sun, Feb 8, 2015 at 1:48 PM, Zeev Suraski wrote: > > > > proposal everyone can rally behind, it very clearly failed. We didn't > > have to wait for a vote by the way, it was clear from the discussion > > on internals@. > > > Controversial RFCs are precisely the ones that SHOULD be voted on. Not really. These should be avoided as much as possible. > Policy states that 2/3s means consensus on core language changes. The > current 63.5% isn't too far from that. Just curious, but do you have a > different number in mind for this vote? 90%? 80%? I'm well aware of it as I wrote that policy. The goal of the policy was to prevent a situation where a temporary majority can introduce features into the language that would later on be impossible to reverse. It's not by any stretch a good mechanism to solve controversial votes, which again, should ideally be avoided as much as possible. It's just that there isn't a better mechanism. Zeev