Hi!
The best (in the sense of "most similar to what we have today") syntax I can think of is to define annotations exactly the same way was you'd define arrays, but replace "array" with the annotation name (plus a prefix). I think this looks like PHP:
We have here at least two non-PHP constructs - %Name meaning "new Name" and array syntax for parameters.
could add a validate() method to ReflectionAnnotation (with an empty default implementation) that subclasses could override to provide their validation logic.
When this validation logic will be called? On getAnnotation()? Then it would be extremely wasteful - the annotation never changes but each time is re-validated anew.
Fair enough, though I find surprising that "parent" forwards. But you'll find that most users don't see LSB as a "scope that is forwarded" but instead as some kind of inheritance mechanism. It also exposed the odd
I don't know how you found out what "most users" of PHP's multi-million user base think - how many millions of people did you ask? - but whoever has wrong preconceptions about how it works should correct them by reading the actual docs. Provided that the actual rule can easily fit on a bumper sticker, I don't think it's too complex.
-- Stanislav Malyshev, Software Architect SugarCRM: http://www.sugarcrm.com/ (408)454-6900 ext. 227 -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
