On 25.06.2018 at 14:30, Zeev Suraski wrote:
> As I mentioned a few days ago I intended to send it slightly later - but as
> Nikita brought up the topic of PHP 8, this is probably as good a time as any
> to start the discussion.
>
> Please note: The goal of this email isn't to discuss in detail
On Wed, Jun 27, 2018 at 2:10 PM, Christoph M. Becker
wrote:
> On 27.06.2018 at 15:00, Jakub Zelenka wrote:
>
> > I think it makes sense for big engine changes that you described but I
> > don't think this should be the case for features in core extensions and
> > SAPI's. The thing is that some of
On 27.06.2018 at 15:00, Jakub Zelenka wrote:
> I think it makes sense for big engine changes that you described but I
> don't think this should be the case for features in core extensions and
> SAPI's. The thing is that some of us are not going to work on those big
> changes for various reasons. P
On Mon, Jun 25, 2018 at 4:03 PM, Zeev Suraski wrote:
> On Mon, Jun 25, 2018 at 5:57 PM Christoph M. Becker
> wrote:
>
> > On 25.06.2018 at 14:30, Zeev Suraski wrote:
> >
> > > What this list is - a collection of directions around which we've
> > performed varying amounts of research (some of the
On Mon, Jun 25, 2018 at 5:57 PM Christoph M. Becker
wrote:
> On 25.06.2018 at 14:30, Zeev Suraski wrote:
>
> > What this list is - a collection of directions around which we've
> performed varying amounts of research (some of them quite a lot, like JIT),
> that I think is strong grounds for us to
On 25.06.2018 at 14:30, Zeev Suraski wrote:
> What this list is - a collection of directions around which we've performed
> varying amounts of research (some of them quite a lot, like JIT), that I
> think is strong grounds for us to start discussing a PHP 8 timeline, and
> making PHP 7.3 the la
