Am 10.05.2011 16:53, schrieb Martin Scotta:

Yes. sure. But I am sure that certain Annotations must be combined to unleash their purpose, no? There is no validation for that, correct?

With the interface approach you can annotate classes, methods, members and parameters, depending on how you build it, no? Annotating functions by themselves...is that really an issue? Since they're mostly stateless why would they need meta-data?

inheriting behaviour is just a special case of inheriting "code" as in traits, no?

interface Annotation { function getParam(); }

interface Annotation {        function getMethodAnnotation($method){                switch( $method ) {                        case 'getSomething': return array('deprecated');                }        } }

I can't argue with that.

What I just noticed is that simple examples (key=>value or even just keywords) are indeed concise and I could imagine using it this way. But for that we have docblocs. But as soon as you go into more complex structures, more than key=>value which guilherme keeps arguing is so essential to the Annotations and is also why we can't use docblocks, it gets unreadable and especially for maintaining state within meta-data, I'd always use PHP-Interfaces over Annotations.