Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:74042 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 27260 invoked from network); 7 May 2014 23:32:23 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 7 May 2014 23:32:23 -0000 Authentication-Results: pb1.pair.com header.from=anatol.php@belski.net; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=anatol.php@belski.net; spf=permerror; sender-id=unknown Received-SPF: error (pb1.pair.com: domain belski.net from 85.214.73.107 cause and error) X-PHP-List-Original-Sender: anatol.php@belski.net X-Host-Fingerprint: 85.214.73.107 klapt.com Received: from [85.214.73.107] ([85.214.73.107:45623] helo=klapt.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 88/75-30354-582CA635 for ; Wed, 07 May 2014 19:32:22 -0400 Received: by klapt.com (Postfix, from userid 33) id 099C223D6106; Thu, 8 May 2014 01:32:18 +0200 (CEST) Received: from 178.7.113.80 (SquirrelMail authenticated user anatol@belski.net) by webmail.klapt.com with HTTP; Thu, 8 May 2014 01:32:18 +0200 Message-ID: <114bb6c05b4b23f60b606eeb89c65371.squirrel@webmail.klapt.com> In-Reply-To: <536A6E34.8090808@oracle.com> References: <536A6E34.8090808@oracle.com> Date: Thu, 8 May 2014 01:32:18 +0200 To: "Christopher Jones" Cc: "Anatol Belski" , "PHP Internals" User-Agent: SquirrelMail/1.5.2 [SVN] MIME-Version: 1.0 Content-Type: text/plain;charset=UTF-8 Content-Transfer-Encoding: 8bit Subject: Re: [PHP-DEV] [RFC] 64 bit platform improvements for string length and integer From: anatol.php@belski.net ("Anatol Belski") Hi Chris, On Wed, May 7, 2014 19:32, Christopher Jones wrote: > > > On 5/6/14, 1:01 AM, Anatol Belski wrote: > >> Hi, >> >> >> I would sincerely invite everyone to the resurrected str_size_and_int64 >> RFC discussion. >> >> >> I propose the discussion to last for one week as allowed by the voting >> RFC >> because this topic has already been discussed to death previously (any >> objections?). As no userland change is introduced, the discussion would >> end and the voting would start on May 13th with 50%+1 votes >> requirement. >> >> https://wiki.php.net/rfc/size_t_and_int64_next >> >> >> Best regards >> >> >> Anatol >> >> > > It seems the "shiny" phpng is attracting all the attention and you are > unlikely to get much discussion: we had so much last time anyway. > > Can you add the proposed voting options to the RFC? Also if you can > resolve the open issue on dead SAPIs first, that would be great. Then lets > vote. > Actually this RFC is being even partly discussed in the parallel phpng thread and on IRC :) These two RFCs definitely intersect and are probably the most significant changes proposed for PHP next. As the voting rule says the discussion "should be at least a week", IMHO lets keep it then (not long till 13th anyway). The vote option would be a simple yes/no choice to accept the RFC for the next major PHP version, just added it. For the SAPI RFC - it's probably not to be solved in such short term of a couple of days (and that's why it was separated from the main one). As it involves trying all the corresponding servers, mailing the authors and waiting for their reaction. Now it also looks like this topic concerns phpng as well. Thus it makes sense firstly to finish the essential change. The task itself of the research and adjoining throw out is a routine. Best Anatol