Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:71048
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.219.42 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <fa05c43bc2fff5420759e05dee19c99f.squirrel@webmail.klapt.com>
References: <fa05c43bc2fff5420759e05dee19c99f.squirrel@webmail.klapt.com>
Date: Fri, 10 Jan 2014 22:42:49 +0100
Message-ID: <CAF+90c8mDBqe+E=cWxpD-U48Ho0QV3iHiwS9pOSEbUn_uZTVnQ@mail.gmail.com>
To: Anatol Belski <ab@php.net>
Cc: PHP Developers Mailing List <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=001a11c1e8b887380504efa49b7a
Subject: Re: [PHP-DEV] [RFC] 64 bit platform improvements for string length
 and integer
From: nikita.ppv@gmail.com (Nikita Popov)

--001a11c1e8b887380504efa49b7a
Content-Type: text/plain; charset=ISO-8859-1

On Fri, Jan 10, 2014 at 3:58 PM, Anatol Belski <ab@php.net> wrote:

> Hi,
>
> https://wiki.php.net/rfc/size_t_and_int64
>
> The discussion time has come. The work on the feature branch continues.
> The current patch is stable enough to be discussed.
>

What is the reason behind the renames of IS_LONG to IS_INT (and Z_LVAL to
Z_IVAL etc), as well as the renames in zpp (s -> S, etc)? Why can't we keep
the old names here? That should reduce the amount of ifndefs involved a
lot, as you'd only have to do it for the type declarations themselves, not
for every single usage. Or is the point here to intentionally provide a
maximum amount of BC breakage, so code doesn't "accidentally" continue to
run (e.g. I think that without the renames extensions could continue to run
mostly without issue on 32bit.)

Nikita

--001a11c1e8b887380504efa49b7a--