Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:76804
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain belski.net from 85.214.73.107 cause and error)
Message-ID: <e0768962293daa3b4e5a5784ce3646b9.squirrel@webmail.klapt.com>
In-Reply-To:
 <CAF+90c_AMJ3SLyX7eDQq-gwFLOCQUfLus+qFfJgAgTzBpZpfEg@mail.gmail.com>
References:
    <CAF+90c_AMJ3SLyX7eDQq-gwFLOCQUfLus+qFfJgAgTzBpZpfEg@mail.gmail.com>
Date: Fri, 22 Aug 2014 14:09:25 +0200
To: "Nikita Popov" <nikita.ppv@gmail.com>
Cc: "PHP internals" <internals@lists.php.net>
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] Better type names for int64 RFC
From: anatol.php@belski.net ("Anatol Belski")

Hi Nikita,

On Fri, August 22, 2014 13:16, 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
>
to be complete, the RFC probably should take in account several new
identifiers which came in (zend_off_t, zend_stat_t and co.). As their
naming scheme is probably somewhat different. I've just documented those
http://git.php.net/?p=php-src.git;a=blob;f=UPGRADING.INTERNALS and
continue.

Regards

Anatol