Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:92619
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.218.51 as permitted sender)
MIME-Version: 1.0
References: <BY2PR0201MB178479B3AF8BD49583233034BF6E0@BY2PR0201MB1784.namprd02.prod.outlook.com>
 <CAEPJdu=EOiMsVpbU8U2diHguaJshWK1DLnKhq=uAHMbHCvuF-w@mail.gmail.com> <5719598E.4000006@zend.com>
In-Reply-To: <5719598E.4000006@zend.com>
Date: Thu, 21 Apr 2016 23:09:31 +0000
Message-ID: <CAJaRsPvvbZrTGbxN-qhMtzhNNhKiXGETFbZjurwX3BxvgQ5Big@mail.gmail.com>
To: Dmitry Stogov <dmitry@zend.com>, Benjamin Eberlei <kontakt@beberlei.de>, 
	PHP internals list <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=001a113ce7a8156f8a053106ce80
Subject: Re: [PHP-DEV] [RFC] PHP Attributes
From: colinodell@gmail.com ("Colin O'Dell")

--001a113ce7a8156f8a053106ce80
Content-Type: text/plain; charset=UTF-8

> A more robust alternative would be something along the same lines that
> Doctrine uses: Make annotations actual classes.

Just spitballing here - what if both approaches were supported, but
class-based annotations were prefixed with a special character (perhaps
"@") to differentiate them?  For example:

<<ArbitraryAnnotation("Hello world")>>
<<@ORM\Entity(table => "foo")>>
class Foo {
    // ...
}

namespace ORM;
class Entity implements \Attribute {
    // ...
}

$r = new ReflectionClass('ORM\Entity');
var_dump($r->getAttributes());

-----

array(2) {
    ["ArbitraryAnnotation"]=>
    string(11) "Hello world"
    ["ORM\Entity"] =>
    object(ORM\Entity)#1 (0) { ... }
}

-----

Again, I'm not necessarily advocating this - just throwing the idea out
there for discussion.

Regards,

Colin

--001a113ce7a8156f8a053106ce80--