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

On 05/06/2016 05:06 AM, Jesse Schalken wrote: If you're going to say "do what you want" with regards to annotations, then just let them be a text string. Parsing the annotation as PHP but not evaluating it as PHP seems a very strange and arbitrary half-way point. If the thing consuming the AST

Re: [PHP-DEV] Forbid dynamic calls to scope introspection/modification functions

Am 29.04.2016 um 11:48 schrieb Nikita Popov: > Welcome to another edition of "crazy PHP edge-cases you don't want > to know about". I love and hate these edge cases at the same time :) > I'd like to introduce a restriction that forbids performing dynamic calls > to scope introspection and modific

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

If you're going to say "do what you want" with regards to annotations, then just let them be a text string. Parsing the annotation as PHP but not evaluating it as PHP seems a very strange and arbitrary half-way point. If the thing consuming the AST is expected to eval() it, then why didn't PHP do t

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

On 5 May 2016 at 15:24, Larry Garfield wrote: > because it doesn't define "right way". Good. > I could easily see, for instance, Doctrine annotations building the > first, PHPUnit the second, and Zend the 3rd. Good! It's not the job of PHP core to tell people how to use annotations. People can

[PHP-DEV] Looking (not very far) ahead to PHP 7.1

Afternoon internals, We are hoping for alpha 1 to be available on June 9th, this is a little over 5 weeks away. Beta 1 (~1 month after alpha 1) on July 7th will be our feature freeze date - no new RFC's can target 7.1 after this date. PHP 7.1 has many things targeting it at the momen

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

Larry Garfield wrote on 05/05/2016 15:24: <> Translator)>> <> <> I could easily see, for instance, Doctrine annotations building the first, PHPUnit the second, and Zend the 3rd. Those would all be legal-ish, but semantically very different. And there's also then no guarantee that $foo >>

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

On 05/05/2016 02:07 AM, Dmitry Stogov wrote: Maybe that's what we want to have here - freedom for everybody to invent their own languages - but I fear the danger of fragmentation here and also people implementing tons of slightly different incompatible parsers for ASTs that are generated. We'd

Re: [PHP-DEV] Re: ext/curl update

On Thu, Apr 28, 2016 at 11:30 PM, Davey Shafik wrote: > I seem to have created some confusion here: > > The reason _my_ patch for Server Push isn't merged is tests for it were > requested and are blocking it. I'm not saying tests for these constants > should be added. > For the record, I'm fine

[PHP-DEV] GOOD Benchmark Results for PHP Master 2016-05-05

Results for project PHP master, build date 2016-05-05 13:12:21+03:00 commit: 5eecd61 previous commit:ee55110 revision date: 2016-05-05 15:18:24+08: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] Attributes/Annotations Case Study: Drupal

Stanislav Malyshev wrote on 05/05/2016 07:48: The key idea of RFC was not to invite another language for meta-data, >but use PHP language itself. This is a good way to avoid handling a lot of issue, but what I am afraid of is that with this solution, what would happen that people start doing exa

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

On 05/05/16 08:34, Dmitry Stogov wrote: >> I think this way can give a good start point with possibility to >> standardize handling of attributes in the future. From the PHP engine >> side, all attributes are AST nodes that can be processed later on the >> userland side. >> > Something like this ma

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

On 05/05/2016 10:24 AM, Alexander Lisachenko wrote: Hello, internals! 2016-05-05 9:48 GMT+03:00 Stanislav Malyshev >: Maybe that's what we want to have here - freedom for everybody to invent their own languages - but I fear the danger of fragmentation

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

Hello, internals! 2016-05-05 9:48 GMT+03:00 Stanislav Malyshev : > Maybe that's what we want to have here - freedom for everybody to invent > their own languages - but I fear the danger of fragmentation here and > also people implementing tons of slightly different incompatible parsers > for AST

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

On 05/05/2016 09:48 AM, Stanislav Malyshev wrote: Hi! It's also possible to write: <> you don't need to split your annotation into many attributes. You should just adopt its syntax to become a valid PHP expression. This expression is not going to be evaluated. It's going to be just parsed