Hi!
> Primarily, I do not see docblocks as the right place to store class' metadata information. Metadata != Comments. I personally regard this as a kind of superstition. There's nothing wrong with extending what can be in comments. In fact, Javascript was officially "HTML comment" for years, and it didn't prevent anybody from using Javascript. There are instances of significant comments in various environments. Outright refusing comments can be significant is just arbitrarily limiting our options for no reason. I don't say it necessarily the best option, but we should not reject it because "oh noes, significant comments!". It has been done, and it's nothing special, just one of the possibilities > This brings the next piece of the puzzle. We have to update lexical and > semantical understanding of PHP. Taking Java's approach (@) does not > work in PHP, because it conflicts with error supression. Same thing Except for the mental context, how @ conflicts with errors? Suppression is always in runtime context and applied to expressions, annotations are always outside of it and apply to declarations. Unless of course you want to annotate variables and closures, but I'm not sure annotating expressions is such a good idea anyway. -- Stanislav Malyshev, Software Architect SugarCRM: http://www.sugarcrm.com/ -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
