> 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 trigge
On Sat, Jun 23, 2018 at 3:23 PM Nikita Popov wrote:
>
> Hi internals,
>
> Based on some recent conversations, I'm getting the impression that after
> PHP 7.3, we might want to go for PHP 8 next.
>
> I'd like to discuss and possibility decide this now, as that would make PHP
> 7.3 the last chance t
Hi
Den søn. 24. jun. 2018 kl. 02.59 skrev Levi Morrison :
> 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.
I
On Sat, Jun 23, 2018 at 4:11 PM Zeev Suraski wrote:
>
>
>
> > -Original Message-
> > From: p...@golemon.com [mailto:p...@golemon.com] On Behalf Of Sara
> > Golemon
> > Sent: Sunday, June 24, 2018 1:07 AM
> > To: Nikita Popov
> > Cc: PHP internals
> > Subject: Re: [PHP-DEV] PHP 8 next?
>
On Sat, Jun 23, 2018 at 5:11 PM, Zeev Suraski wrote:
>> On Sat, Jun 23, 2018 at 4:22 PM, Nikita Popov wrote:
>> > Based on some recent conversations, I'm getting the impression that
>> > after PHP 7.3, we might want to go for PHP 8 next.
>> >
>> > I'd like to discuss and possibility decide this n
Hello,
> On Jun 23, 2018, at 6:38 PM, Alice Wonder wrote:
>
>> On 06/23/2018 03:11 PM, Zeev Suraski wrote:
>>
>> This is slightly earlier than I intended to bring it up but I do too think
>> that the next version beyond 7.3 should be 8.
>
> I disagree.
>
> I'm mostly a user, not a PHP devel
On Sat, Jun 23, 2018 at 6:39 PM Alice Wonder wrote:
> On 06/23/2018 03:11 PM, Zeev Suraski wrote:
> >
> >
> >> -Original Message-
> >> From: p...@golemon.com [mailto:p...@golemon.com] On Behalf Of Sara
> >> Golemon
> >> Sent: Sunday, June 24, 2018 1:07 AM
> >> To: Nikita Popov
> >> Cc: P
On 06/23/2018 03:11 PM, Zeev Suraski wrote:
-Original Message-
From: p...@golemon.com [mailto:p...@golemon.com] On Behalf Of Sara
Golemon
Sent: Sunday, June 24, 2018 1:07 AM
To: Nikita Popov
Cc: PHP internals
Subject: Re: [PHP-DEV] PHP 8 next?
On Sat, Jun 23, 2018 at 4:22 PM, Nikita
> -Original Message-
> From: p...@golemon.com [mailto:p...@golemon.com] On Behalf Of Sara
> Golemon
> Sent: Sunday, June 24, 2018 1:07 AM
> To: Nikita Popov
> Cc: PHP internals
> Subject: Re: [PHP-DEV] PHP 8 next?
>
> On Sat, Jun 23, 2018 at 4:22 PM, Nikita Popov wrote:
> > Based on s
On Sat, Jun 23, 2018 at 4:22 PM, Nikita Popov wrote:
> Based on some recent conversations, I'm getting the impression that after
> PHP 7.3, we might want to go for PHP 8 next.
>
> I'd like to discuss and possibility decide this now, as that would make PHP
> 7.3 the last chance to get in deprecatio
Hi internals,
Based on some recent conversations, I'm getting the impression that after
PHP 7.3, we might want to go for PHP 8 next.
I'd like to discuss and possibility decide this now, as that would make PHP
7.3 the last chance to get in deprecations.
Nikita
Someone was asking about memcache vs memached on IRC the other day and I
advised them the memcache extension looked abandoned based on the PECL
page. Having 2 such similar extensions is confusing - It would also be
nice if someone could document the major differences between the 2
extensions so
Rowan Collins in php.internals (Fri, 22 Jun 2018 23:40:27 +0100):
>However, it seems that the package without a d is actually abandoned.
>The official PECL package was last released more than 5 years ago [3],
>and the bug asking for PHP 7 compatibility is still open [4]. An
>unofficial fork appa
13 matches
Mail list logo
