Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:76834
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain zend.com designates 209.85.220.179 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CAF+90c_AMJ3SLyX7eDQq-gwFLOCQUfLus+qFfJgAgTzBpZpfEg@mail.gmail.com>
References: <CAF+90c_AMJ3SLyX7eDQq-gwFLOCQUfLus+qFfJgAgTzBpZpfEg@mail.gmail.com>
Date: Sat, 23 Aug 2014 13:55:23 +0400
Message-ID: <CA+9eiLsvFG1M7ngzEF+071mi0bKnqObSu9J71v6fjDYEyWNbeg@mail.gmail.com>
To: Nikita Popov <nikita.ppv@gmail.com>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=001a11c1eb68cd4e6d050148f3dc
Subject: Re: [PHP-DEV] [RFC] Better type names for int64 RFC
From: dmitry@zend.com (Dmitry Stogov)

--001a11c1eb68cd4e6d050148f3dc
Content-Type: text/plain; charset=UTF-8

100% agree with RFC.
It would be great if technical improvements wouldn't be messed with this
renaming :(

Thanks. Dmitry,




On Fri, Aug 22, 2014 at 3:16 PM, Nikita Popov <nikita.ppv@gmail.com> 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
>

--001a11c1eb68cd4e6d050148f3dc--