Re: [RFC] 64 bit platform improvements for string length and integer

From: Date: Thu, 23 Jan 2014 17:26:36 +0000
Subject: Re: [RFC] 64 bit platform improvements for string length and integer
References: 1 2 3 4 5 6 7 8 9 10  Groups: php.internals 
Request: Send a blank email to internals+get-71448@lists.php.net to get a copy of this message
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

« previous php.internals (#71448) next »