Do we really need to mimic the PHP syntax in annotations? As for me I don't like the idea of having to print quotes for key names and arrows just for that. Also to migrate to a new engine from old doctrine parser I just had to do search-replace the @orm: with @ORM\ - now it leads to more work to be done for migrating.
Is it case sensitive? @var loads the Annotation\Var - does that mean that it's not? What about adding custom Annotation namespace for current library usage (DI config stage)? For example somebody already uses a class that has some strange annotations (@test for example) and I extend that class with the one which is parsed by annotation reader. It could be that the class with strange annotations is from some vendor and I cannot modify it to add written-by-me empty classes (why doing that?) namespace for that strange annotations. The only good solution is to teach the annotation parser to use more then \Annotation namespace to search for classes before throwing an Exception. Or maybe to exclude inherited classes from some namespace? Both ways to have maximum flexibility? -- 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
