One of the advantage of classes vs array is that you have to create
the class and define its structure and behaviour before using it.
For example you cannot do with Array something like the [Inherited] annotation :
[Inherited]
class SampleAnnotation extends ReflectionAnnotation {}
How could you define that the SampleAnnotation annotation is Inherited
or not if you define it on the fly ?
Pierrick
2010/8/25 Benjamin Eberlei <kont...@beberlei.de>:
>
> Hi Pierrick,
>
> Awesome RFC! :) I think this is a really useful addition on many levels.
>
> We had a chat about this yesterday, i just wanted to throw it into the
> discussion here again:
>
> I think a solution where "->getAnnotations()" returns only an array of the
> annotations data is simpler to use.
> Validation of the data would have to be done by the user in this case, but
> you could of course
> add a layer in PHP that transforms this data into an object structure.
>
> greetings,
> Benjamin
>
> On Wed, 25 Aug 2010 08:56:53 -0400, Pierrick Charron
> <pierr...@webstart.fr>
> wrote:
>> Hello PHP Internals!
>>
>> Recently a RFC was included on the PHP Wiki[1].
>> I know there've been a lot of buzz related to PHP 5.4, but this is not
>> the subject of this email.
>>
>> I'm here to propose a new feature in PHP: Annotations.
>> A patch is already available with 54 tests for the moment[2].
>>
>> I worked together with Guilherme Blanco to make this support happen in
>> a fresh PHP SVN trunk checkout.
>> Please review, comment and provide feedback! I think it's a very
>> useful support and may benefit users a lot.
>>
>> [1] http://wiki.php.net/rfc/annotations
>> [2] http://www.adoy.net/php/Annotations.diff
>>
>> Regards,
>> Pierrick
>>
>> (Sorry if you receive this message twice but it looks like I have
>> problems with the ML)
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
