If this one is okay (from the logic perspective/coding), please let me know and don't merge until I wrote the docs for it (I noticed it's the only way to get me to write docs =_= )

What if two modules depend on each other?

@marc-mabe makes no real sense since modules have a loading order. The feature can be turned off at any time btw. It's just a safety check before letting the spaceship starts the engines.

@Ocramius As it's only a check does it make sense to check it after loading.
Circular dependencies could make sense on closed environments like company internal modules.

@marc-mabe loading (including init triggers) may depend on other modules anyway. That's why I do it so early. Even tempted to handle it before autoloading eventually.

@Ocramius Is the loading process not known the list of modules for loading - isn't it?
So the loading order could be changed automatically to load depended modules first?
To support circular dependencies the module itself need to say which dependencies are required for initialization and which are required after the loading process finished.

Does this make sense ?

@marc-mabe no, my point is exactly to AVOID any kind of magic here. It's just a check. If you know what you're doing, you can turn it off and handle dependencies as you wish.

This is just a very important thing for people who may (example) install ZfcUserDoctrineORM and don't enable ZfcUser, and in turn forget to enable ZfcBase. This is a self-documenting exception that helps beginners in getting started, nothing more. No changing of anything :)

And yes, it would just help discovering circular dependencies. Doesn't mean it has to solve 'em :)

@Ocramius I'm on you. Because it's a development feature and can be disabled - circular dependencies aren't a must-have and too much magic isn't good.

AFAIK, this is complete

Implementation looks straightforward. I like it. Good work!

Done, rebased

Looks good. The only issue I have is similar to what @prolic says: getDependencyModules doesn't read well, and is hard to understand. May I suggest getModuleDependencies()? If you agree, I can even make such a change at merge time.

Merged -- see a087928