Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:71894 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 57407 invoked from network); 31 Jan 2014 21:21:40 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 31 Jan 2014 21:21:40 -0000 Authentication-Results: pb1.pair.com smtp.mail=zeev@zend.com; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=zeev@zend.com; sender-id=unknown Received-SPF: error (pb1.pair.com: domain zend.com from 209.85.212.41 cause and error) X-PHP-List-Original-Sender: zeev@zend.com X-Host-Fingerprint: 209.85.212.41 mail-vb0-f41.google.com Received: from [209.85.212.41] ([209.85.212.41:35295] helo=mail-vb0-f41.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id EA/A0-54292-3E31CE25 for ; Fri, 31 Jan 2014 16:21:40 -0500 Received: by mail-vb0-f41.google.com with SMTP id g10so3421223vbg.28 for ; Fri, 31 Jan 2014 13:21:37 -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:content-type :content-transfer-encoding; bh=hp3RoY4gHbMiLdyNsweUkWMiKmVuB3q8J53I2ivQkpY=; b=fbTEbxz+CUFUnvAgtNzXUIfapS3/XaL8P4zKb7IsFoKNoi3xIg36C3px99/Kg/lUBr 8mjIVjmWgLIWEX4gWHsBSccua90JctN7dHXzjBMSwl5hfNMh2gGL4R8tGYRJNQTtAR+Z ijaNL4EtgKuiHM8T5S4NY/5qJZQv330xsVmOSt0xnqe0Oz7xjEyNKOVzVSTgl9ENsEwQ gysK540bGu9laVVtTh8d2ihXn9NW2qv/ZyaUvbC5bZGq0AzEoqabmHYlIU6xaC5d00f6 1qp0jypivmQF3fVkKWu8nFO1uwDGXoeXJUuPVWL2pQ1SCSUhFkgWhf5Y2/1VMSmwD6t2 eg4g== X-Gm-Message-State: ALoCoQnZeUXXavItu8i2/317pqruFPzMKoMekLMRrJnGDQCgx5FxSn5dJL7KTiHb/apppSmdGp+uPtI5uKpjqKBAJp5dHmQKTvjDgza2bHgWVf9PzaihzhcclBJ5/3bc7V7hN2MdaAKq X-Received: by 10.52.37.103 with SMTP id x7mr22950vdj.75.1391203297455; Fri, 31 Jan 2014 13:21:37 -0800 (PST) References: <1391171792.2941.130.camel@guybrush> <52EB9A16.5060605@phpdoc.de> <1391172906.2941.140.camel@guybrush> In-Reply-To: <1391172906.2941.140.camel@guybrush> MIME-Version: 1.0 X-Mailer: Microsoft Outlook 14.0 thread-index: AQKXG/MFvR0atL/ck2TgW5/Clbz6gwIG1ZhUAfRCZyUCOGo/GJjdvbxw Date: Fri, 31 Jan 2014 23:21:36 +0200 Message-ID: <9810c708a9fcc543a263365b5d7c2a63@mail.gmail.com> To: internals@lists.php.net Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Subject: RE: [PHP-DEV] [VOTE] 64 bit platform improvements for string length and integer From: zeev@zend.com (Zeev Suraski) > -----Original Message----- > From: Johannes Schl=C3=BCter [mailto:johannes@schlueters.de] > Sent: Friday, January 31, 2014 2:55 PM > To: Ulf Wendel > Cc: internals@lists.php.net > Subject: Re: [PHP-DEV] [VOTE] 64 bit platform improvements for string > length and integer > > On Fri, 2014-01-31 at 13:41 +0100, Ulf Wendel wrote: > > Am 31.01.2014 13:36, schrieb Johannes Schl=C3=BCter: > > > I think adding this patch to 5.x therefore would be quite some > > > bending of that rule and that combined with the fact that it is late > > > makes me believe that proposing this for 5.6 is illegal. > > > > Are you saying the RFC is 'illegal' ? If the subject proposed is not > > allowed, it would make litte sense collecting votes. > > I think the RM has to reject this from 5.6 independently from the voting > result as he is bound by the release process RFC. All, I have to add something here. Many of the people voting on that RFC have never ever contributed as much a= s a single line of code into the PHP source tree, and a couple have literally contributed low-single-digit patches. Incidentally, as far as I could tell, all of them[*] voted in favor of the proposed changes (i.e. source compatibility breakage). Even though having non-code-contributors makes a lot of sense for decisions regarding the language's features and we built in support for it in the voting RFC, in my opinion, it makes no sense at all for people who have no stake at the development of the language's source code to weigh in on how that code is written. Personally I didn't expect we'd be voting on things like that (implementation style) back when I was involved in the voting RFC= , but perhaps it's time to amend it a bit. If you fall in that category, please do the right thing and delete your vote. Zeev