On 08/16/2014 12:52 AM, Pierre Joye wrote:
On Sat, Aug 16, 2014 at 12:49 AM, David Soria Parra wrote:
On 2014-08-15, Pierre Joye wrote:
Let me summerize a few things that have come up:
(1) phpng doesn't justify PHP7
It does. It's a complete new engine. It has performance improvements
Am 16.08.2014 um 00:19 schrieb David Soria Parra:
> My main concern with this is that it's php6 all over again.
That is my fear, too.
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
On Aug 16, 2014 1:57 AM, "Jonathan Wage" wrote:
>
> I agree with Derick, Zeev and Sebastian.
>
> It seems more economical at this point for everyone to join together and
> focus our efforts on PHP 7.
Short term? Maybe, if we forget that the period will be more 6-7 months.
Long term? An economical
On Aug 16, 2014 4:11 AM, "Jan Ehrhardt" wrote:
>
> Christoph Becker in php.internals (Sat, 16 Aug 2014 01:33:28 +0200):
> >Wim Godden wrote:
> >
> >> On 16/08/2014 0:43, Pierre Joye wrote:
> >>> Here we have two issues, whether or not we need a 5.x to prepare 7
and if
> >>> one year Dev time is en
Christoph Becker in php.internals (Sat, 16 Aug 2014 01:33:28 +0200):
>Wim Godden wrote:
>
>> On 16/08/2014 0:43, Pierre Joye wrote:
>>> Here we have two issues, whether or not we need a 5.x to prepare 7 and if
>>> one year Dev time is enough.
>>
>> IMHO, that'll depend on which feature will be add
I agree with Derick, Zeev and Sebastian.
It seems more economical at this point for everyone to join together and
focus our efforts on PHP 7.
I also think we should be bold and target the PHP 7 release for one year
from now. If everyone gets on board and works towards the same goal it is
possible
Hi all,
On Fri, Aug 15, 2014 at 9:48 AM, Andrea Faulds wrote:
> I’ve kept putting this off, but given the current “move phpng to master”
> vote, I really can’t delay this any longer.
>
> It looks like PHP 7 is going to happen and phpng will be the base of that.
> While we could move straight to
Wim Godden wrote:
> On 16/08/2014 0:43, Pierre Joye wrote:
>> Here we have two issues, whether or not we need a 5.x to prepare 7 and if
>> one year Dev time is enough.
>
> IMHO, that'll depend on which feature will be added/changed/refactored
> for 7. I might have missed that discussion, but so f
On 16/08/2014 0:43, Pierre Joye wrote:
Here we have two issues, whether or not we need a 5.x to prepare 7 and if
one year Dev time is enough.
IMHO, that'll depend on which feature will be added/changed/refactored
for 7. I might have missed that discussion, but so far I haven't seen a
wishlist
On Sat, Aug 16, 2014 at 12:49 AM, David Soria Parra wrote:
> On 2014-08-15, Pierre Joye wrote:
>> --001a1133979e094b370500b2c0a9
>> Content-Type: text/plain; charset=UTF-8
>>
>> On Aug 16, 2014 12:20 AM, "David Soria Parra" wrote:
>> (didn't
>>> we learn anything from PHP 6?).
>>
>> I did. And w
On 2014-08-15, Pierre Joye wrote:
> --001a1133979e094b370500b2c0a9
> Content-Type: text/plain; charset=UTF-8
>
> On Aug 16, 2014 12:20 AM, "David Soria Parra" wrote:
> (didn't
>> we learn anything from PHP 6?).
>
> I did. And with opcache. Both with hypothetical deadlines based on
> arbitrary ran
On Aug 16, 2014 12:20 AM, "David Soria Parra" wrote:
(didn't
> we learn anything from PHP 6?).
I did. And with opcache. Both with hypothetical deadlines based on
arbitrary random facts about the status or stability.
Here we have two issues, whether or not we need a 5.x to prepare 7 and if
one ye
On 2014-08-15, Ferenc Kovacs wrote:
> --001a11c1258a38c82a0500a8b070
> Content-Type: text/plain; charset=UTF-8
> Content-Transfer-Encoding: quoted-printable
> we don't have a single instance where we were able to deliver a minor
> release under a year, and I'm fairly sure that 7.0 will see more pr
On 15 Aug 2014, at 15:51, Sebastian Bergmann wrote:
> With regard to the scope of PHP 7, I think it would be great to limit
> ourselves to "infrastructure" improvements (new executor from PHPNG,
> AST-based compiler (plus userland extension that provides access to
> the AST) from Nikita) and cle
Am 15.08.2014 um 02:48 schrieb Andrea Faulds:
> As PHP 7 may break backwards-compatibility, 5.7 gives us a chance to add
> deprecation warnings and such to help people prepare for 7.
If the only changes that PHP 5.7 introduces (as compared to PHP 5.6) are
deprecation warnings for features remov
> proposed in the multiple default arguments RFC.
Sorry, multiple default blocks in a switch statement RFC.
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
On 15 Aug 2014, at 11:43, Ferenc Kovacs wrote:
> On Fri, Aug 15, 2014 at 11:25 AM, Derick Rethans wrote:
>
>> Basically, you're wanting to give up hope on PHP 7 in one year *at the
>> moment it is started*... I think that's a pretty big mistake to do this
>> already. The momentum is here now,
I'm not completely sure about others in this thread, but my personal
view is that PHP 5.7 should be released at around the same time as PHP
7. It should contain E_DEPRECATED warnings where applicable, such as
proposed in the multiple default arguments RFC. I've also heard talk
of removing some feat
Derick Rethans wrote (on 15/08/2014):
On Fri, 15 Aug 2014, Andrea Faulds wrote:
I’ve kept putting this off, but given the current “move phpng to
master” vote, I really can’t delay this any longer.
It looks like PHP 7 is going to happen and phpng will be the base of
that. While we could move st
On Aug 15, 2014 12:43 PM, "Ferenc Kovacs" wrote:
>
> On Fri, Aug 15, 2014 at 11:25 AM, Derick Rethans wrote:
>
> > On Fri, 15 Aug 2014, Andrea Faulds wrote:
> >
> > > I’ve kept putting this off, but given the current “move phpng to
> > > master” vote, I really can’t delay this any longer.
> > >
>
On Fri, Aug 15, 2014 at 11:25 AM, Derick Rethans wrote:
> On Fri, 15 Aug 2014, Andrea Faulds wrote:
>
> > I’ve kept putting this off, but given the current “move phpng to
> > master” vote, I really can’t delay this any longer.
> >
> > It looks like PHP 7 is going to happen and phpng will be the b
Am 15.08.2014 um 11:25 schrieb Derick Rethans:
> Basically, you're wanting to give up hope on PHP 7 in one year *at the
> moment it is started*... I think that's a pretty big mistake to do this
> already. The momentum is here now, let's use it to get PHP 7
> ready—instead of bogging ourselves do
> -Original Message-
> From: Derick Rethans [mailto:der...@php.net]
> Sent: Friday, August 15, 2014 12:25 PM
> To: Andrea Faulds
> Cc: PHP internals
> Subject: Re: [PHP-DEV] Let's make a 5.7 release
>
> On Fri, 15 Aug 2014, Andrea Faulds wrote:
>
> >
On Fri, Aug 15, 2014 at 11:25 AM, Derick Rethans wrote:
> On Fri, 15 Aug 2014, Andrea Faulds wrote:
>
>> I’ve kept putting this off, but given the current “move phpng to
>> master” vote, I really can’t delay this any longer.
>>
>> It looks like PHP 7 is going to happen and phpng will be the base o
On Fri, 15 Aug 2014, Andrea Faulds wrote:
> I’ve kept putting this off, but given the current “move phpng to
> master” vote, I really can’t delay this any longer.
>
> It looks like PHP 7 is going to happen and phpng will be the base of
> that. While we could move straight to PHP 7 after the rel
On 15 Aug 2014, at 02:06, Levi Morrison wrote:
>> As PHP 7 may break backwards-compatibility, 5.7 gives us a chance to add
>> deprecation warnings and such to help people prepare for 7.
>
> The updated multiple default blocks in a switch statement proposes
> exactly this. Even if PHP 5.7 doesn
> As PHP 7 may break backwards-compatibility, 5.7 gives us a chance to add
> deprecation warnings and such to help people prepare for 7.
The updated multiple default blocks in a switch statement proposes
exactly this. Even if PHP 5.7 doesn't have any features I think it
would make the transition
27 matches
Mail list logo
