Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:71866
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain schlueters.de from 217.114.215.10 cause and error)
To: Anatol Belski <ab@php.net>
Cc: PHP Developers Mailing List <internals@lists.php.net>, Matt Ficken
 <mattficken@php.net>, "Stephen A. Zarkos" <szarkos@php.net>
In-Reply-To: <e0681b3331094323d383a048471790f8.squirrel@webmail.klapt.com>
References: <e0681b3331094323d383a048471790f8.squirrel@webmail.klapt.com>
Content-Type: text/plain; charset="UTF-8"
Date: Fri, 31 Jan 2014 13:36:32 +0100
Message-ID: <1391171792.2941.130.camel@guybrush>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] [VOTE] 64 bit platform improvements for string
 length and integer
From: johannes@schlueters.de (Johannes =?ISO-8859-1?Q?Schl=FCter?=)

On Mon, 2014-01-27 at 21:15 +0100, Anatol Belski wrote:
> https://wiki.php.net/rfc/size_t_and_int64

It is my understanding that part of the reason for the release workflow
RFC was that if patches miss the mark they don't have to wait for long
till the next release comes.

In this case here we have 5.6.0alpaha1 out. Adding a major API change
touching each and every file can't be added to 5.6 anymore.


Also the release process RFC says

         x.y.z to x.y+1.z
            [...]
            ABI and API can be broken (internals), src compatibility
        should
            be kept if possible, while breakages are allowed

This rule contains many things that "can" and "should" and thus is open
to interprettation. In my interpretation this rule is meant to allow
small changes, affecting only few extensions and where it would be
stupid to defer the.

I think adding this patch to 5.x therefore would be quite some bending
of that rule and that combined with the fact that it is late makes me
believe that proposing this for 5.6 is illegal.

johannes