Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:92637
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain zend.com designates 157.56.111.144 as permitted sender)
To: Dominic Grostate <codekestrel@googlemail.com>
CC: PHP internals <internals@lists.php.net>
Thread-Topic: [PHP-DEV] [RFC] PHP Attributes
Thread-Index: AQHRnBAun0yJJJCyoUaLowSO4sZVN5+VD36AgAA6G4CAAGECRIAALPC5
Date: Fri, 22 Apr 2016 11:13:34 +0000
Message-ID: <BY2PR0201MB1784832421A06C2B244AE1B1BF6F0@BY2PR0201MB1784.namprd02.prod.outlook.com>
References: <BY2PR0201MB178479B3AF8BD49583233034BF6E0@BY2PR0201MB1784.namprd02.prod.outlook.com>
	<CAFKaYMqg6H2YAgS-ATjcYtXw8GLbp_Kr+VuZFMRPZTkAS1g0hA@mail.gmail.com>
	<571965D1.9020102@zend.com>
	<CAFKaYMqAcp=G3cbHh56BFC+F1pff_Ld-PBgyMnrmphb9e0VRAw@mail.gmail.com>
	<CAFKaYMqLW9=rcdFDE2sBK=3Tu_S6_4uPNNgMJXoyMDRLBNnU1A@mail.gmail.com>,<CAFKaYMqk5=e4N9V7ni870jzm9dNKP1x5g2KG=aAEbcWkhd5VrQ@mail.gmail.com>
In-Reply-To: <CAFKaYMqk5=e4N9V7ni870jzm9dNKP1x5g2KG=aAEbcWkhd5VrQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
spamdiagnosticoutput: 1:23
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative;
	boundary="_000_BY2PR0201MB1784832421A06C2B244AE1B1BF6F0BY2PR0201MB1784_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-originalarrivaltime: 22 Apr 2016 11:13:34.2095
 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 32210298-c08b-4829-8097-6b12c025a892
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BY2PR0201MB1782
Subject: Re: [PHP-DEV] [RFC] PHP Attributes
From: dmitry@zend.com (Dmitry Stogov)

--_000_BY2PR0201MB1784832421A06C2B244AE1B1BF6F0BY2PR0201MB1784_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<<Entry>> works fine


sapi/cli/php attr6.php
array(1) {
  ["Entity"]=3D>
  bool(true)
}


$ cat attr6.php
<?php
<<Entity>>
function foo() {}
$r =3D new ReflectionFunction("foo");
var_dump($r->getAttributes());
?>
[dmitry@tpl2 CGI-DEBUG]$ sapi/cli/php attr6.php
array(1) {
  ["Entity"]=3D>
  bool(true)
}


<<ORM\Entity>> - doesn't work now, but I'll implement this and extend RFC o=
n next week.


Thanks. Dmitry.

________________________________
From: Dominic Grostate <codekestrel@googlemail.com>
Sent: Friday, April 22, 2016 11:31
To: Dmitry Stogov
Cc: PHP internals
Subject: Re: [PHP-DEV] [RFC] PHP Attributes


I'm having a crack at it now.  Seeing if I can use it to plug a new Annotat=
ion driver for Doctrine.

Couple of things I've found so far are:

<<Entity>> with empty args doesn't work.
<<ORM\Entity>> namespace doesn't work.

On the subject of using @, that could denote a class constructor, unless so=
meone already mentioned that.

On 22 Apr 2016 12:44 a.m., "Dmitry Stogov" <dmitry@zend.com<mailto:dmitry@z=
end.com>> wrote:


On 04/22/2016 02:16 AM, Dominic Grostate wrote:

This is amazing.  It would actually allow us to implement our automated ass=
ertions ourselves, as opposed to requiring it within the language.

this was the idea - to give a good tool instead of implementing every possi=
ble use-case in the language.



Could it also support references?

<<sanitize(&$a)>>
function foo($a) {

}

yes. "&$a" is a valid PHP expression.

If you plan to use this, I would appreciate, if you to build the patched PH=
P and try it.
The early we find problems the better feature we will get at the end.

Thanks. Dmitry.


On 21 Apr 2016 10:13 p.m., "Dmitry Stogov" <dmitry@zend.com<mailto:dmitry@z=
end.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 expressi=
ons as attribute values.

These expressions are not evaluated, but stored as Abstract Syntax Trees, a=
nd later may be accessed (node by node) in PHP extensions, preprocessors an=
d PHP scripts their selves. I think this ability may be useful for "Design =
By Contract", other formal verification systems, Aspect Oriented Programmin=
g, etc


https://wiki.php.net/rfc/attributes


Note that this approach is going to be native, in contrast to doc-comment a=
pproach that uses not well defined syntax, and even not parsed by PHP itsel=
f.


Additional ideas, endorsement and criticism are welcome.


Thanks. Dmitry.


--_000_BY2PR0201MB1784832421A06C2B244AE1B1BF6F0BY2PR0201MB1784_--