Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:76822 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 32127 invoked from network); 22 Aug 2014 18:38:47 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 22 Aug 2014 18:38:47 -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.54 as permitted sender) X-PHP-List-Original-Sender: pierre.php@gmail.com X-Host-Fingerprint: 209.85.216.54 mail-qa0-f54.google.com Received: from [209.85.216.54] ([209.85.216.54:60839] helo=mail-qa0-f54.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 8A/D3-10436-53E87F35 for ; Fri, 22 Aug 2014 14:38:46 -0400 Received: by mail-qa0-f54.google.com with SMTP id k15so10219331qaq.27 for ; Fri, 22 Aug 2014 11:38:43 -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=Pww1uJONhIKvxonS7NnLJL+dpko17p3tTAEpoWV9d3Q=; b=RR0UHI9+Zn1exlp9lv9SnfaNRjExbxgZvmUIH53m4L+Tzmuv6b+o1q4SO+TJwv79JO 0CWHvCOB6Ohhb7a6cYQKEzooGPYs6VI+ILicS9Sj6hytAECuNCaoqkinPTgkNzQ7a3mv yB3xl0a7Hhbw0J7qmtjUatuyNWwC7DtijoByydYS+eINkGHYywKXb9/LWRZIvmqp4JBz sJtraEvUosJGDUDmOkRdQYnZPSXaMsHV/fA6F4/lF9wnW+u5QVc/l5L0d+j0Kmxo1NJb vHQhe8bhYv3hnFrwT9dB3GpkUv0Bg9TiSUEVOgiP09+bTm6I6amitm1WMQHC9b4xVeYN +gfg== MIME-Version: 1.0 X-Received: by 10.229.57.138 with SMTP id c10mr10763909qch.30.1408732723553; Fri, 22 Aug 2014 11:38:43 -0700 (PDT) Received: by 10.140.95.146 with HTTP; Fri, 22 Aug 2014 11:38:43 -0700 (PDT) Received: by 10.140.95.146 with HTTP; Fri, 22 Aug 2014 11:38:43 -0700 (PDT) In-Reply-To: References: Date: Fri, 22 Aug 2014 20:38:43 +0200 Message-ID: To: Andrea Faulds Cc: PHP internals , Nikita Popov Content-Type: multipart/alternative; boundary=001a1133112e922c4b05013c25cc Subject: Re: [PHP-DEV] [RFC] Better type names for int64 RFC From: pierre.php@gmail.com (Pierre Joye) --001a1133112e922c4b05013c25cc Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Aug 22, 2014 5:33 PM, "Andrea Faulds" wrote: > > > On 22 Aug 2014, at 12:16, Nikita Popov wrote: > > > 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=E2=80=99m very much in favour of this RFC. It is not necessary to chang= e the type names after all; if people turn on compiler warnings, they=E2=80=99ll = find out what=E2=80=99s broken anyway. That's one of my points. They won't for all cases. And why good names reflecting the underlying type will help. It is what the 1st version if the int64 rfc did. --001a1133112e922c4b05013c25cc--