Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:71700
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.214.182 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CAEZPtU6rvmrfrX73jRim1pz-76t8ThdAkOoP-0ygc3KG9GaxUw@mail.gmail.com>
References: <e0681b3331094323d383a048471790f8.squirrel@webmail.klapt.com>
	<CAF+90c-W+un8BsBD3OAeVL05s3iM5RxGnOD2Xa7nBPC+TuPijg@mail.gmail.com>
	<CAEZPtU6rvmrfrX73jRim1pz-76t8ThdAkOoP-0ygc3KG9GaxUw@mail.gmail.com>
Date: Tue, 28 Jan 2014 21:51:13 +0100
Message-ID: <CAF+90c8-ELB=jw3V5HiJLMSU4tTUypjP-EgMpnYzDXuHLFsNxg@mail.gmail.com>
To: Pierre Joye <pierre.php@gmail.com>
Cc: Anatol Belski <ab@php.net>, PHP Developers Mailing List <internals@lists.php.net>, 
	Matt Ficken <mattficken@php.net>, "Stephen A. Zarkos" <szarkos@php.net>
Content-Type: multipart/alternative; boundary=001a11332d1624aa4404f10dfc83
Subject: Re: [PHP-DEV] [VOTE] 64 bit platform improvements for string length
 and integer
From: nikita.ppv@gmail.com (Nikita Popov)

--001a11332d1624aa4404f10dfc83
Content-Type: text/plain; charset=ISO-8859-1

On Tue, Jan 28, 2014 at 9:33 PM, Pierre Joye <pierre.php@gmail.com> wrote:

> > Just to clarify my vote: I voted "No" on the RFC, but only because I
> think
> > the major extension source API break is better suited to PHP 6 than PHP
> > 5.6. I fully support merging this into master, as the first change for
> PHP
> > 6.
>
> Sad. As the work for pecl extensions is really not as large as you
> think, fairly straight forward. The vote for php6 is not running now.
> There is no option for PHP 6 as what can be done in php 6 internally
> is much larger and would allow more breakage. On the other side, we
> provide options to minimize the work for the extensions developers in
> order of magnitude smaller than the changes we introduced in the past
> for the OO APIs for example.  Anyway, sad that you voted no for
> something as important than true 64bit support.
>

Maybe I'm indeed overestimating the impact. Could you please link to the
source-code for a PECL (or other third-party) extension that was ported to
be compatible with the new API, so people can see the actual impact this
makes? (Hopefully some ext that requires compat across multiple versions
like 5.3+ and has non-trivial amount of code and functions, like a few
dozen.) I couldn't find an example in RFC, but maybe I just missed it. Only
saw small snippets in there.

Nikita

--001a11332d1624aa4404f10dfc83--