On 24 January 2014 01:26, Christopher Jones
<[email protected]> wrote:
> 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
This is pretty much how I feel about this too. As a user, it's
something I'd like to have, but as a maintainer or developer on a few
extensions (some PECL, some third party), this isn't something I'm
terribly excited about having on a few months notice for 5.6 — it's
going to be an annoying, subtle change for code that has to support
older versions, as worthwhile as it is in the long term.
I think Nikita's earlier point upthread about it being something that
feels like a major version feature is a potentially a good one. I'm
happy enough with it being in 5.7 if we still don't have any plans for
5++ in 6-12 months, but if we end up starting to work on a 5++
simultaneously with 5.7 (which I could see happening, given recent
threads on Internals), then it may even be better held off for that.
Adam