> I really liked this at first, but then after thinking about ti for a > while, it means that if one day we'd have a standard annotation feature, > we couldn't build on existing annotations, a documentation parser > couldn't use our reader because it wouldn't support docblocks, people > would have to use @var(int) and such.. And that sounds a bit bad to me.
Having a special class named "var" and importing some namespace for using the standart docblocks is also not that good as I think. Doctrine Annotation parser is good for all the use-cases of using annotations for something _special_, be it entity annotations or validation purpose, not for generating documentation from the existing code. -- If you want to report a vulnerability issue on symfony, please send it to security at symfony-project.com You received this message because you are subscribed to the Google Groups "symfony developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/symfony-devs?hl=en
