Pros and Cons:
+ clear separation of projects and responsibilities
The current naming convention better separates projects and
responsibilities. All re-usable and independent libraries are under
Component\. Straightforward to document and to understand.
How putting everything under the same namespace makes for a better
separation?
+ logical structure for people unrelated to Symfony
Again, how can someone not aware of Symfony make a difference between
Symfony\EventDispatcher and Symfony\CMF now. I don't even see how we can
document that as everything is at the same level but some have very
different purposes.
- BC break, but can be fixed in an automated fashion by recursively
renaming all namespaces
Another drawback (not a major one though): The notion of Symfony
Components disappears. It's probably just about marketing if you want,
but Symfony2 adoption will probably be much better if we can demonstrate
that we actually have decoupled components.
I'm not against the change as I was the one who proposed something
similar some time ago
(http://groups.google.com/group/symfony-devs/browse_thread/thread/01723c9cae0140fc),
but I quite don't understand why people who were opposed to the change
are now in favor of it.
Fabien
--
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
