Noting Kris' comment that #2 might jive well with what XML already does, I think #3 feels most natural for PHP. Annotation aliases seem directly analogous to native use statements, which really are just aliasing a full class path under a shorter name.
Would it be too much trouble to support use-as? Regarding duplicate class names, I think we might do well to mimic PHP and throw exceptions up front when a conflict is detected. Ultimately, these annotation prefixes are just shortcuts anyway, right? From what I recall with doctrine-common's reader, you can skip short notation and use the full class name following the "@" symbol. If that's true, I see it as all the more reason to mimic PHP's class/namespace handling. -- 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
