Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:92617
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain zend.com designates 157.56.111.113 as permitted sender)
To: Benjamin Eberlei <kontakt@beberlei.de>, PHP internals list
	<internals@lists.php.net>
References: <BY2PR0201MB178479B3AF8BD49583233034BF6E0@BY2PR0201MB1784.namprd02.prod.outlook.com>
 <CAEPJdu=EOiMsVpbU8U2diHguaJshWK1DLnKhq=uAHMbHCvuF-w@mail.gmail.com>
Message-ID: <5719598E.4000006@zend.com>
Date: Fri, 22 Apr 2016 01:51:58 +0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101
 Thunderbird/38.7.1
MIME-Version: 1.0
In-Reply-To: <CAEPJdu=EOiMsVpbU8U2diHguaJshWK1DLnKhq=uAHMbHCvuF-w@mail.gmail.com>
Content-Type: multipart/alternative;
	boundary="------------050801040402000502010507"
SpamDiagnosticOutput: 1:23
SpamDiagnosticMetadata: NSPM
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 21 Apr 2016 22:52:13.3919 (UTC)
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CY1PR0201MB1788
Subject: Re: [PHP-DEV] [RFC] PHP Attributes
From: dmitry@zend.com (Dmitry Stogov)

--------------050801040402000502010507
Content-Type: text/plain; charset="utf-8"; format=flowed
Content-Transfer-Encoding: 7bit



On 04/22/2016 01:03 AM, Benjamin Eberlei wrote:
>
> On Thu, Apr 21, 2016 at 11:13 PM, Dmitry Stogov <dmitry@zend.com 
> <mailto:dmitry@zend.com>> wrote:
>
>     Hi,
>
>
>     I would like to present an RFC proposing support for native
>     annotation.
>
>     The naming, syntax and behavior are mostly influenced by HHVM
>     Hack, but not exactly the same.
>
>     The most interesting difference is an ability to use arbitrary PHP
>     expressions as attribute values.
>
>     These expressions are not evaluated, but stored as Abstract Syntax
>     Trees, and later may be accessed (node by node) in PHP extensions,
>     preprocessors and PHP scripts their selves. I think this ability
>     may be useful for "Design By Contract", other formal verification
>     systems, Aspect Oriented Programming, etc
>
>
>     https://wiki.php.net/rfc/attributes
>
>
>     Note that this approach is going to be native, in contrast to
>     doc-comment approach that uses not well defined syntax, and even
>     not parsed by PHP itself.
>
>
>     Additional ideas, endorsement and criticism are welcome.
>
>
> I love it!
>
> Syntax is good, and i like that it just returns plain arrays. 
> Everything else (more formal) can be added on top by Doctrine 
> Annotations for example.

thanks for support :)
>
> About expressions, isn't there an ambigoutiy? <<test(1)>> is a "plain" 
> name, value based attribute. But it could also be an ast\node of a 
> function call to "test(1)"
even in AST scalars are scalars.
so <<test(1+2)>> would return: ast\node "+" with two children int(1) and 
int(2).

> I am wondering if they shouldn't get their own start/end signs to 
> clear that up, <<<test(1)>> vs <<test(1)>>.

no need for extra complication.

Thanks. Dmitry.


--------------050801040402000502010507--