Re: [PHP-DEV] [VOTE][RESULTS] 7.1 RMs selection

Hey all, As Joe said, thanks for voting, and we have lots of work ahead of us to make sure that 7.1 is a solid release — I'll do my best to ensure that happens! - Davey On Tue, May 3, 2016 at 10:01 PM, Joe Watkins wrote: > Morning internals, > > Thanks for voting :)

Re: [PHP-DEV] Re: async/await - is future reserved words in PHP 7.x?

> I don't think we should wait, I was just thinking that it might not be ready > until that time. > > Also, if we plan on rewriting streams and I/O to all be async and use libuv > underneath, that would probably be a BC break unless the existing functions > just become blocking interfaces for a

Re: [PHP-DEV] Re: async/await - is future reserved words in PHP 7.x?

On 05/04/2016 11:44 AM, Niklas Keller wrote: 2016-05-04 16:40 GMT+02:00 Stephen Coakley : Why do we have to wait until PHP 8? Should be mostly backwards compatible and be fine in 7.2 or so. Issue is probably more deciding on an API. I don't think we should wait, I was

Re: [PHP-DEV] Re: async/await - is future reserved words in PHP 7.x?

>> /Legend speaks of such plans, but they come and go in whispers. Like a >> shadow, or a mist from the east. The prophecy spake of such features >> targeting PHP8; lo, most believe it to be myth./ > > > Why do we have to wait until PHP 8? Should be mostly backwards compatible > and be fine in 7.2

Re: [PHP-DEV] Re: async/await - is future reserved words in PHP 7.x?

2016-05-04 16:40 GMT+02:00 Stephen Coakley : > On 05/04/2016 05:59 AM, S.A.N wrote: > >> EventLoop interface, on development stage: >> https://github.com/async-interop/event-loop >> > > That's a userland design for event loops; async/await and coroutines don't >

[PHP-DEV] The death of `#ifndef FAST_ZPP`?

Hi everyone, You may recall that PHP 7.0 introduced a new API for processing arguments to internal functions, the "Fast Parameter Parsing API" or FAST_ZPP (https://wiki.php.net/rfc/fast_zpp), which is an alternative to the existing zend_parse_parameters function family. Since FAST_ZPP was

[PHP-DEV] BAD Benchmark Results for PHP Master 2016-05-04

Results for project PHP master, build date 2016-05-04 11:14:20+03:00 commit: ee55110 previous commit:153b27d revision date: 2016-05-03 19:11:15+02:00 environment:Haswell-EP cpu:Intel(R) Xeon(R) CPU E5-2699 v3 @ 2.30GHz 2x18 cores, stepping 2, LLC 45 MB

Re: [PHP-DEV] Re: async/await - is future reserved words in PHP 7.x?

On 05/04/2016 05:59 AM, S.A.N wrote: EventLoop interface, on development stage: https://github.com/async-interop/event-loop That's a userland design for event loops; async/await and coroutines don't necessarily depend on an event loop. They could be added to the language without an event

Re: [PHP-DEV] Attributes/Annotations Case Study: Drupal

On 4 May 2016 10:41 pm, "Rowan Collins" wrote: > > > You could either think of this as "setting lots of variables": > > new Foo { $bar = 1, $baz = 2 } > > or you could think of it as "an object literal like an array literal": > > new Foo { 'bar' => 1, 'baz' => 2 } > I

Re: [PHP-DEV] Attributes/Annotations Case Study: Drupal

Jesse Schalken wrote on 04/05/2016 13:20: (maybe there should be a $ before the property names, not sure) And there's the rub! :P When named parameters have been discussed before, there was a lot of bikeshedding over what the syntax should look like, and this is arguably a very similar

Re: [PHP-DEV] Attributes/Annotations Case Study: Drupal

On Sat, Apr 30, 2016 at 9:47 AM, Larry Garfield wrote: > 3) Some way to provide a data definition for the annotation that can be > checked at compile time. This could be classes, a la Doctrine. It could be > a new Annotation type as others have suggested. It could be

Re: [PHP-DEV] Re: async/await - is future reserved words in PHP 7.x?

> I think we can spoonfeed the massive undertaking a bit by spreading it > across several iterations just to get things going. An idea I had was to > just begin by providing coroutines as part of the language. That would > include a `\Coroutine` class, as well as await / async keywords. This would

Re: [PHP-DEV] zend_pass_function/zif_pass

On Wed, 4 May 2016, Dmitry Stogov wrote: > I don't see a big problem exporting zif_pass, if this's really necessary. Bob already committed that, and I've a PR for Xdebug too: https://github.com/xdebug/xdebug/pull/271/commits/c4a539d75f0d2546e9d0cb0dbc06f5a7a31f447e cheers, Derick >

Re: [PHP-DEV] [RFC] Pipe Operator

On Sun, May 1, 2016 at 4:05 AM, Larry Garfield wrote: > > In a way... Sara, this syntax feels like it's only one step removed from > promises; if any of the chained steps involve IO, it becomes basically what > promises are for. Am I barking down the wrong tree, or is

Re: [PHP-DEV] zend_pass_function/zif_pass

Morning Dmitry, Bob already exported it. http://git.php.net/?p=php-src.git;a=commit;h=f59de7ea368da55f1f21ca82810febb3cdec06f0 Cheers Joe On Wed, May 4, 2016 at 7:28 AM, Dmitry Stogov wrote: > I don't see a big problem exporting zif_pass, if this's really necessary. > >

Re: Fwd: [PHP-DEV] [RFC] PHP Attributes

Hi Fleshgrinder On Fri, Apr 29, 2016 at 4:42 AM, Fleshgrinder wrote: > Is there a reason why you think that Design by Contract (DbC) should be > implemented via annotations/attributes? It's not complement of DbC, although it could be used. Basic DbC idea is "Do

Re: [PHP-DEV] zend_pass_function/zif_pass

I don't see a big problem exporting zif_pass, if this's really necessary. Thanks. Dmitry. From: Nikita Popov Sent: Saturday, April 30, 2016 8:40:54 PM To: Derick Rethans Cc: Dmitry Stogov; PHP Developers Mailing List Subject: Re: [PHP-DEV]