Re: [PHP-DEV] Re: [RFC] [VOTE] Short Closures

Hi, As a PHP developer, I agree with the possible confusion between `->` and `~>`. `==>` is a better choice IMHO, for its similarity with Hacklang syntax, as said previously. Thanks. *Julien BENOIT* *PHP & JS developer @GuestToGuest * Paris, FR.

[PHP-DEV] Re: Windows OpCache bug fix

Ops, I forgot to revert the exit condition. http://git.php.net/?p=php-src.git;a=commitdiff;h=2d55e8c186ef1034c2af64478da8f23dbeb28be9 On Thu, Sep 24, 2015 at 11:00 AM, Dmitry Stogov wrote: > hi Matt, > > Thanks. > I also moved the exit condition to be before Sleep(). > This

Re: [PHP-DEV] Re: [RFC] [VOTE] Short Closures

Den 2015-09-24 kl. 09:10, skrev Stanislav Malyshev: Hi! As a PHP developer, I agree with the possible confusion between `->` and `~>`. `==>` is a better choice IMHO, for its similarity with Hacklang syntax, as said previously. I'm getting a feeling the RFC could be more successful if syntax

Re: [PHP-DEV] Re: [RFC] [VOTE] Short Closures

Lester Caine wrote on 24/09/2015 08:06: So is PHP heading down the path of a compiled language even if that is hidden in some automatic cache or is it still mainly an interpreted script? PHP already is a compiled language; it just has a highly dynamic runtime engine (which is at times a

Re: [PHP-DEV] zend_parse_parameters changes not fully documented in phpng-upgrading, PR to fix existing tools

On Wed, 23 Sep 2015, Sean DuBois wrote: > Hey list, > > 'l' had a change 'long' -> 'zend_long' and 's' had a change 'int' -> > 'size_t'. > > These two changes are really hard to catch when porting an extension, > nothing complains at compile time, you don't get segfaults when > calling

Re: [PHP-DEV] PHP 7.1 - Address PHPSadness #28?

François Laupretre wrote on 23/09/2015 22:17: Le 23/09/2015 18:37, Stig Bakken a écrit : If they start replacing calls to isset()/array_key_exists() with exists(), that's their choice and it can only improve overall readability. The thing is, it won't really improve overall readability,

Re: [PHP-DEV] Re: [RFC] [VOTE] Short Closures

Hi! > As a PHP developer, I agree with the possible confusion between `->` and > `~>`. > `==>` is a better choice IMHO, for its similarity with Hacklang syntax, as > said previously. I'm getting a feeling the RFC could be more successful if syntax was made a choice between ~> and ==> as a voting

Re: [PHP-DEV] Re: [RFC] [VOTE] Short Closures

On Sep 24, 2015 2:11 PM, "Stanislav Malyshev" wrote: > > Hi! > > > As a PHP developer, I agree with the possible confusion between `->` and > > `~>`. > > `==>` is a better choice IMHO, for its similarity with Hacklang syntax, as > > said previously. > > I'm getting a feeling

Re: [PHP-DEV] Re: [RFC] [VOTE] Short Closures

Changed my vote to "no" after thinking further into it: - I don't like the usage of the tilde: `->` and `~>` are too similar and easily confused - Using `==>` would align PHP further to hacklang, which is a plus - I'm still conflicted on automatically importing all of the scope into the

[PHP-DEV] Re: Windows OpCache bug fix

hi Matt, Thanks. I also moved the exit condition to be before Sleep(). This should prevent race condition on last iteration (after unlocked sleep process should try to reattach). Committed to PHP-7.0 and master.

[PHP-DEV] Re: Windows OpCache bug fix

Ops, I forgot to revert the exit condition. http://git.php.net/?p=php-src.git;a=commitdiff;h=2d55e8c186ef1034c2af64478da8f23dbeb28be9 On Thu, Sep 24, 2015 at 11:00 AM, Dmitry Stogov wrote: > hi Matt, > > Thanks. > I also moved the exit condition to be before Sleep(). > This

Re: [PHP-DEV] Re: [RFC] [VOTE] Short Closures

On Sep 22, 2015 10:16 PM, "Andrea Faulds" wrote: > > I am unhappy with the ~> syntax choice. As I've mentioned before, it's hard to type for many people, it looks too much like ->, and it's unnecessarily different from Hack's ==>, of which this RFC would otherwise be proposing a

Re: [PHP-DEV] Re: [RFC] [VOTE] Short Closures

On 24/09/15 07:39, Marco Pivetta wrote: > - I'm still conflicted on automatically importing all of the scope into > the closure: while it is working for functional languages, that's where > most of the headaches come from in languages such as javascript. Isn't this the crux of some decisions?

[PHP-DEV] Unicode regex roadmap

While PCRE2 upgraded to Unicode version 8, PCRE, which is in maintenance mode, will presumably remain on Unicode version 7 indefinitely. Does PHP have a roadmap for up-to-date regex, either with PCRE2 or some other lib? Tom

Re: [PHP-DEV] Re: [RFC] [VOTE] Short Closures

On 24/09/2015 07:39, Marco Pivetta wrote: - I'm still conflicted on automatically importing all of the scope into the closure: while it is working for functional languages, that's where most of the headaches come from in languages such as javascript. The automatic import IMO isn't as much an

Re: [PHP-DEV] zend_parse_parameters changes not fully documented in phpng-upgrading, PR to fix existing tools

On Thu, Sep 24, 2015 at 11:01:09AM +0100, Derick Rethans wrote: > On Wed, 23 Sep 2015, Sean DuBois wrote: > > > Hey list, > > > > 'l' had a change 'long' -> 'zend_long' and 's' had a change 'int' -> > > 'size_t'. > > > > These two changes are really hard to catch when porting an extension, > >

[PHP-DEV] Benchmark Results for PHP Master 2015-09-24

Results for project php-src-nightly, build date 2015-09-24 16:39:43+03:00 commit: 3b5120c14775e517501ec497ad8b87091c91926e revision_date: 2015-09-24 14:20:07+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] PHP 7.1 - Address PHPSadness #28?

Rowan Collins wrote on 23/09/2015 21:15: On 23 September 2015 20:04:57 BST, Ryan Pallas wrote: I dislike this because it makes refactoring harder. What's more, the function is not dereferencing a variable to get its value, it is looking up a name in the symbol table, so

Re: [PHP-DEV] Re: [RFC] [VOTE] Short Closures

On 24 September 2015 19:21:20 BST, Stanislav Malyshev wrote: >> How does one then address that this RFC only covers a subset of >> Hacklang functionality when having the same operator? > >Why one should address it? PHP is a different language, and we are >under >no

Re: [PHP-DEV] Re: [RFC] [VOTE] Short Closures

Hi! > How does one then address that this RFC only covers a subset of > Hacklang functionality when having the same operator? Why one should address it? PHP is a different language, and we are under no obligation to completely match functionality of any other language. -- Stas Malyshev

Re: [PHP-DEV] Data serialization of objects, want to iterate 'sealed' properties then dynamic ones

Thank you for this, Sean! I'm making headway for php 5.5/5.6. This should come in handy when/if I get around to PHP 7. On Wed, Sep 23, 2015 at 3:35 PM, Sean DuBois wrote: > On Wed, Sep 23, 2015 at 02:16:39PM -0700, j adams wrote: > > Not my intention to be combative, but what

Re: [PHP-DEV] Re: [RFC] [VOTE] Short Closures

Den 2015-09-24 kl. 20:21, skrev Stanislav Malyshev: Hi! How does one then address that this RFC only covers a subset of Hacklang functionality when having the same operator? Why one should address it? PHP is a different language, and we are under no obligation to completely match

Re: [PHP-DEV] Re: [RFC] [VOTE] Short Closures

Den 2015-09-22 kl. 17:16, skrev Andrea Faulds: Hi Bob, Bob Weinand wrote: Hey, Thanks for all your feedback in the discussion thread! So, before I start the vote, just two quick notes: I've added two notes about the statement syntax and the single variable use. Though a few people

Re: [PHP-DEV] Data serialization of objects, want to iterate 'sealed' properties then dynamic ones

On 23/09/2015 22:16, j adams wrote: Not my intention to be combative, but what abouthttp://php.net/pcntl_fork ? I've used that before in a robust distributed application that runs without any intervention for months. It's my understanding that PHP is thread safe, but not itself multithreaded. I

Re: [PHP-DEV] Re: [RFC] [DISCUSSION] More precise float value

Hi Anatol, On Tue, Sep 22, 2015 at 4:35 AM, Anatol Belski wrote: >> -Original Message- >> From: yohg...@gmail.com [mailto:yohg...@gmail.com] On Behalf Of Yasuo >> Ohgaki >> Sent: Sunday, September 20, 2015 11:49 PM >> To: Kalle Sommer Nielsen >> Cc:

Re: [PHP-DEV] Re: [RFC] [VOTE] Short Closures

On Sep 24, 2015 09:07, "Lester Caine" wrote: > > On 24/09/15 07:39, Marco Pivetta wrote: > > - I'm still conflicted on automatically importing all of the scope into > > the closure: while it is working for functional languages, that's where > > most of the headaches come from

[PHP-DEV] RFC: Generics

Hi Ben & Internals, I spent most of today and yesterday just getting used to the parser language. I was able to implement the basic syntax on most of the constructs, just to get a partial proof of concept going. https://github.com/orolyn/php-src/commit/ee731240eab1e5986152cadaaca6d3e5b921ba7d

Re: [PHP-DEV] Data serialization of objects, want to iterate 'sealed' properties then dynamic ones

Thanks, Rowan, for the clarification! And no, this is not my primary question. At the risk of irritating everyone, here are the questions I need answered: 1) Is there not any way to first iterate through the default properties and then iterate through *only the dynamic properties* ?

Re: [PHP-DEV] Re: [RFC] [VOTE] Short Closures

Stas, On Thu, Sep 24, 2015 at 2:21 PM, Stanislav Malyshev wrote: > Hi! > >> How does one then address that this RFC only covers a subset of >> Hacklang functionality when having the same operator? > > Why one should address it? PHP is a different language, and we are under >

Re: [PHP-DEV] Re: [RFC] [DISCUSSION] More precise float value

Hi all, On Fri, Sep 25, 2015 at 7:49 AM, Yasuo Ohgaki wrote: > No problem. I'll update so that 0 mode is for 7.1. > JSON's is better to use larger precision. So this change is targeted > to 5.6 and 7.0. > > Let me know if you have comments on this. The RFC is updated.

[PHP-DEV] new foo()->bar() syntax error : "new" associativity

Hi all, https://bugs.php.net/bug.php?id=70549 It seems this is better to be fixed in near future. Let "new" be associative? Currently, it's syntax error. Was there discussion for this with https://wiki.php.net/rfc/uniform_variable_syntax ? Regards, -- Yasuo Ohgaki yohg...@ohgaki.net -- PHP