Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:71448
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain oracle.com designates 141.146.126.69 as permitted sender)
Message-ID: <52E150CC.8080202@oracle.com>
Date: Thu, 23 Jan 2014 09:26:36 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: internals@lists.php.net
References: <fa05c43bc2fff5420759e05dee19c99f.squirrel@webmail.klapt.com>	<CAF+90c8mDBqe+E=cWxpD-U48Ho0QV3iHiwS9pOSEbUn_uZTVnQ@mail.gmail.com>	<CA+9eiLvhRqFAunM8GCpqE5ja2jXKCzFMKdtF0NkBT11nu=36MQ@mail.gmail.com>	<CAEZPtU7-mBoXcsvXQvD42uG58KKKLY3TJL=aV5uqcGEFhE3PKQ@mail.gmail.com>	<CAEZPtU7vJDEyZAeCPR3j7_4+HL-4iCMUd3+Xa94xzg7xe1Z91Q@mail.gmail.com>	<52E0F55F.4040802@lsces.co.uk>	<CAF+90c8E6cKh7bt5KDdhxZso=sheNMGyLgdjA+9zckqoOL8jMg@mail.gmail.com>	<CAEp07h-Ga7oTMn3CQXqHXEAbe8EO6V8adz8joAV8g2DHMd8bpw@mail.gmail.com>	<CAF+90c-GCkuJsbyh0GA_0Fh6oUOr6-WOJ6_3deb=NA-sSVCODQ@mail.gmail.com> <CAEZPtU6HJshvMJVmrxH5QyOasFRD16kRXJ07JH8oHS=iK9i0Sg@mail.gmail.com>
In-Reply-To: <CAEZPtU6HJshvMJVmrxH5QyOasFRD16kRXJ07JH8oHS=iK9i0Sg@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] [RFC] 64 bit platform improvements for string length
 and integer
From: christopher.jones@oracle.com (Christopher Jones)



On 1/23/14 7:53 AM, Pierre Joye wrote:
> On Jan 23, 2014 4:48 PM, "Nikita Popov"
>> Updating bundled extensions is simple because you only need to support the
>> new APIs, whereas third-party extensions need to support multiple PHP
>> versions - if the API changes so drastically that is complicated.
>
> It does not change drastically. Check the patch. It can maybe even give
> less required changes, see the open questions.
>
> Cheers,
>

I would call the changes required in each extension drastic because of
their wide spread scope and potential for introducing problems.  If
you look at the merges to OCI8 yesterday (which were in addition to
the basic porting Anatol did some time back), you can see a couple of
forward merges had been missed, and some subtle type change breakages
were picked up QA.

Regarding your comment yesterday about being at the start of the
release, I disagree.  This may be an English language subtlety which
isn't worth arguing over: my main point remains that such a big change
should have more time to mature in a main development branch before
reaching users.  (The release cycle started when PHP 5.5 was branched.
Where we are now is beginning the process of releasing, which is
different.)

Overall
  - I'm fine with changes going into, say, PHP 5.7
  - I'm fine with the type renaming
  - I'd prefer ZPP compatibility was kept
  - I'm fine with dropping support for old SAPIs, but I think warning
    is needed no matter how unusable they currently are e.g. this means
    merging the feature to PHP 5.7

Chris

-- 
christopher.jones@oracle.com  http://twitter.com/ghrd
Free PHP & Oracle book:
http://www.oracle.com/technetwork/topics/php/underground-php-oracle-manual-098250.html