Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:76806 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 81055 invoked from network); 22 Aug 2014 12:17:07 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 22 Aug 2014 12:17:07 -0000 Authentication-Results: pb1.pair.com header.from=pierre.php@gmail.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=pierre.php@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.216.49 as permitted sender) X-PHP-List-Original-Sender: pierre.php@gmail.com X-Host-Fingerprint: 209.85.216.49 mail-qa0-f49.google.com Received: from [209.85.216.49] ([209.85.216.49:46912] helo=mail-qa0-f49.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 00/60-13566-2C437F35 for ; Fri, 22 Aug 2014 08:17:06 -0400 Received: by mail-qa0-f49.google.com with SMTP id dc16so9527771qab.22 for ; Fri, 22 Aug 2014 05:17:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=EqfUgXjcoYRw1RnaHy0auScHMZJC5rTVXmCo/Rdy38I=; b=rGaTR4iDn0eL4plw3QS5U6Wg0e52BnKsKDik+rJFoIaIyETyMatuzLNZHaKWVStxlO p+5SLcTsJXWHqvYdfRuWvasPyPBlNNgvCHp0wzhNBpuCIHgJ6bktyodyYPCdkZS5UgIp NT2kvE925MCPWK0+hVU/XSZ9yNYJK8iLs03Uqf7K0ToHpmqikAzpcGji6MEwkVPRr/yQ n3wG9mQtFh4ongT97iCVqoMa987VfylNfMZGD3ovGf5AUFVSbpuGppOD6vuSKUj+imS1 Qex2HEB6l9Ip7IRSRwKo+GwQYrpvhxKFwJti1xGLTISgl+eElBEJRe1lMatj47KTscLG C7CQ== MIME-Version: 1.0 X-Received: by 10.140.30.66 with SMTP id c60mr6989630qgc.30.1408709824386; Fri, 22 Aug 2014 05:17:04 -0700 (PDT) Received: by 10.140.95.146 with HTTP; Fri, 22 Aug 2014 05:17:04 -0700 (PDT) In-Reply-To: References: Date: Fri, 22 Aug 2014 14:17:04 +0200 Message-ID: To: Nikita Popov Cc: PHP internals Content-Type: text/plain; charset=UTF-8 Subject: Re: [PHP-DEV] [RFC] Better type names for int64 RFC From: pierre.php@gmail.com (Pierre Joye) On Fri, Aug 22, 2014 at 1:16 PM, Nikita Popov wrote: > Hi internals! > > Today the int64 RFC has been merged, despite objections regarding the > naming changes it introduces. > > As we were not given a chance to resolve this issue before the merge, a > short proposal has been created, which aims to revert all unnecessary > naming changes and instead use type names that are consistent with the > existing code base and expectations: > > https://wiki.php.net/rfc/better_type_names_for_int64 > > Due to the unexpected merge on short notice, with no chance for discussion, > this issue is blocking a number of other patches. As such I ask if we can > move through this RFC with a shortened cycle. I would not appreciate having > to wait three weeks to have a workable codebase again. I also request to let me add options for actual good naming (see my previous reply). I would also strongly suggest to group these renaming actions in one RFC and get rid of it in the next couple of weeks (following the usual periods for a RFC). STR macros being on top of my list. And I'd to remember that we suffer from double standards while you guys do whatever you want with ng, and certainly with ast as well. I wonder what you would say if we begin to be as picky and keep asking to change things for months :/ Cheers, -- Pierre @pierrejoye | http://www.libgd.org