On Thu Nov 18 08:34 AM, guilhermebla...@gmail.com wrote: > Hi Larry, > > For existent project examples and usage, here are 2 links of the > upcoming versions of Doctrine 2 and Symfony 2: > > http://www.doctrine-project.org/projects/orm/2.0/docs/reference/basic- > mapping/en#introduction-to-docblock-annotations > http://docs.symfony-reloaded.org/guides/validator.html > > Please understand that Roman, Benjamin, Jonathan and I wrote this > Annotation parser for Doctrine, which was reused by Bernhard on > Symfony. > So I have clean understanding of the issue we have on hands and every > single point that it is required to address. That's why I wrote the > RFC. >
I'm really confused about the "issue", no objections have been made for a docblock parser for "annotations". That can easily live as PECL extension, Doctrine ORM mapping can done in XML, YAML, docblock annotations,... symphony validation in XML, YAML, docblock annotations, ...? Why is it such a persistent *issue* to have language level annotations? Because people want their decorative data around class properties? Java developers who want their hibernate? For uses cases in java (annotations as hints to the compiler): http://video.google.com/videoplay?docid=-1531727105949862857# Does this even apply to php? Hints to the parser? Optimizations? I'll say it again, I'm not against annotations but copying java and its mistakes is not the way to go. Remember that vendors (oracle, bea,...) love annotations to sell their tools, in orm hibernate won. Please improve the RFC to address php-specific problems Now, I'm going to go back and listen to that song "sugar, sugar" by the archies -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
