Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:76798 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 63740 invoked from network); 22 Aug 2014 11:27:59 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 22 Aug 2014 11:27:59 -0000 Authentication-Results: pb1.pair.com header.from=pthreads@pthreads.org; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=pthreads@pthreads.org; spf=permerror; sender-id=unknown Received-SPF: error (pb1.pair.com: domain pthreads.org from 74.125.82.43 cause and error) X-PHP-List-Original-Sender: pthreads@pthreads.org X-Host-Fingerprint: 74.125.82.43 mail-wg0-f43.google.com Received: from [74.125.82.43] ([74.125.82.43:43599] helo=mail-wg0-f43.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id FC/CA-09530-D3927F35 for ; Fri, 22 Aug 2014 07:27:58 -0400 Received: by mail-wg0-f43.google.com with SMTP id l18so10366674wgh.14 for ; Fri, 22 Aug 2014 04:27:54 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:subject:from:to:cc:date:in-reply-to :references:content-type:mime-version:content-transfer-encoding; bh=ShNrSeyykFT3+OIeKK3JdK2U3OwOKvk75aUQaEIuNeQ=; b=BRfGWPRGZIZegBBwhDrR3T4Frun6hv83fzU4rBv7tCj7SJqgr6Az+1R4WxWsN0OpUx iZf9Q5DT7mnkloHMwcwiXmGBF3Hei5E6S9bdfR6mIVOLKA5z/GN8MOGq7HZcI8Vq7af/ SQ2wVTptfsqe6LpkA5SCFZhucHf5AXJGoprBRTsGjvR1t/1WahrUiGMi+rTFtHp3CCI1 Xs3QUQAXVnCnTbWIlswoP6UHvp8BTwotefnvL14tq2o6LF4aWI6TFim8/ryijZTGPJhS mlykZrfEks9UgJH9hUPN2TqFmwpbOdF7+52by0cqybPIVTOjZQ3u1+rLZHDRAh3geipS VT2Q== X-Gm-Message-State: ALoCoQmsKLO47k/Z90mHjaFY5FupZ7NLYoSsVuTa3EiImSECo/SnG3zpDiiuY04amnwbwYmZPhGU X-Received: by 10.180.75.14 with SMTP id y14mr10267551wiv.79.1408706874572; Fri, 22 Aug 2014 04:27:54 -0700 (PDT) Received: from [192.168.1.67] (host86-163-225-243.range86-163.btcentralplus.com. [86.163.225.243]) by mx.google.com with ESMTPSA id el3sm30289087wib.24.2014.08.22.04.27.53 for (version=TLSv1 cipher=RC4-SHA bits=128/128); Fri, 22 Aug 2014 04:27:53 -0700 (PDT) Message-ID: <1408706872.13437.2.camel@localhost.localdomain> To: Nikita Popov Cc: PHP internals Date: Fri, 22 Aug 2014 12:27:52 +0100 In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.10.4 (3.10.4-3.fc20) Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] [RFC] Better type names for int64 RFC From: pthreads@pthreads.org (Joe Watkins) On Fri, 2014-08-22 at 13:16 +0200, 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. > > Nikita Morning internals, I'd very much like the same as Nikita; that's expected names, and quickly. Already it is going to be extremely difficult to maintain extensions for