Re: PHP 8 next?
| From: | Levi Morrison | Date: | Sun, 24 Jun 2018 14:31:18 +0000 |
| Subject: | Re: PHP 8 next? | ||
| References: | 1 2 3 4 5 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-102391@lists.php.net to get a copy of this message | ||
On Sun, Jun 24, 2018 at 12:47 AM Zeev Suraski <zeev@zend.com> wrote:
>
> > Neither JIT nor FFI require backwards compatibility breaks in language. I don't
> > think either of those particular features would substantially break the C API
> > either. If these are the motivations for PHP 8 then I strongly object.
>
> Backwards compatibility breakages have never been the trigger for bumping into a major release.
> They were *allowed* in case a major release was made available - for different reasons.
>
> The trigger for a major release has always been very substantial improvements/changes to the
> language, which I believe JIT, FFI and potentially async squarely fit into (and I'll explain
> why I think that separately later this week). This is true for PHP 3, 4, 5 and 7 (even though 3 and
> 5 did introduce inherent compatibility breakages as a part of its new functionality).
My position stands: I *strongly* object. If we rush to PHP 8 then it
will be at least 4-5 more years before we have another chance for
breakages in PHP 9. We can add features yearly.