You are right, I could leave the original autoloader but it introduces a dependency with atoum and, for a production code, it could be something that the user does not want.

That's why I removed the autoloader from the project and used the one provided by composer in unit tests, so that, the dependency on atoum is clear and only for test purpose.

If the user does not use composer, I think he should put his own autoloading strategy.

To me, introducing a dependency on atoum only for autoloading purpose is not a good thing but I also can revert those changes to get both ;)

_This should also answer the [next comment](https://github.com/mageekguy/mehen/pull/3#discussion_r7981894)_