On 19.04.2011 21:51, Benjamin Eberlei wrote: > I would like to point out that except (1) nothing is possible at all > with the Doctrine Annotations Parser without a heavy rewrite. > > The problem is easily described: > > Any method or variable block has no access to the context of classes. If > that would be done for every variable and method doc block you have to > parse the class header and add the context to the variable/method > parsing process. > > While I understand your concern with wanting to fix the @extra issue i > am still wondering why not change the annotation prefixes to @security. > > I doubt there will be a huge amount of annotations prefixes with future > bundles that might lead to clashes. additionally it would be trivial for > bundle implementors to make the prefix configurable on demand.
+1. We're trying to keep the two bundles under the "extra" context for simplicity's sake, and the resulting disambiguation solutions are ten times more complex to explain to people. Sounds wrong to me. If we really have to do this, then I'm all for (1) if it works, or (3) for it's relative simplicity. (2), sure it "worked" for XML except that most people are confused as hell by xml namespaces. Cheers -- Jordi Boggiano @seldaek :: http://seld.be/ -- 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 symfony-devs@googlegroups.com To unsubscribe from this group, send email to symfony-devs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/symfony-devs?hl=en
