Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:71118
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.217.172 as permitted sender)
MIME-Version: 1.0
Sender: yohgaki@gmail.com
In-Reply-To: <1389654319.6953.45.camel@ghost>
References: <fa05c43bc2fff5420759e05dee19c99f.squirrel@webmail.klapt.com>
 <CAGa2bXbfpRriHzCTdFaboCfT_afH=0W2NsK0OJVBrHhdNLk5dQ@mail.gmail.com> <1389654319.6953.45.camel@ghost>
Date: Tue, 14 Jan 2014 09:20:57 +0900
Message-ID: <CAGa2bXYCb4iuYYuxCfsX1tDALJXV+x5TYUDwJ=Ogtm7YdfE8dA@mail.gmail.com>
To: Anatol Belski <ab@php.net>
Cc: PHP Developers Mailing List <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=001a1133a2aeec372204efe32c0f
Subject: Re: [PHP-DEV] [RFC] 64 bit platform improvements for string length
 and integer
From: yohgaki@ohgaki.net (Yasuo Ohgaki)

--001a1133a2aeec372204efe32c0f
Content-Type: text/plain; charset=UTF-8

Hi Anatol,

On Tue, Jan 14, 2014 at 8:05 AM, Anatol Belski <ab@php.net> wrote:

> thanks for the interest on this. Such an idea existed at the start among
> others, as well as introducing a new zval member for 'int64' besides
> 'long'. The reasons for not doing it (now), also from the todays point
> of view:
>
> - much higher patch complexity
> - with more complexity the risk of not finishing the patch grows
> - worse compatibility with libraries
> - worse compatibility with existing extensions
> - 64 bit processors are widely available
> - well, the slowliness you mention, whereby i've no benchmarks at hand
>

Thank you for your explanations.
These are understandable reasons.

Let's finish current proposal, then we may try to extend int type.
If I finished my todo list for PHP, I'll join your project!

Regards,

--
Yasuo Ohgaki
yohgaki@ohgaki.net

--001a1133a2aeec372204efe32c0f--