The ClassLoader component doc documents only the deprecated class

[stof]

The only class documented in the component doc is UniversalClassLoader, which is deprecated as of 2.1 in favor of the ClassLoader one (or composer).

None of the 2.1+ classes (the ClassLoader being similar to the Composer autoloader and able to be configured from a composer-generated namespace map, and the different decorating cached loaders able to wrap both class loaders) are documented while they should be the one used.
Thus, documenting the cached loaders could be useful as this is where the component provides some additional value compared to the composer class loader.

[xabbuh]

Does it make sense to throw away the documentation on the UniversalClassLoader and only reuse some of it for the ClassLoader?

I would go for documenting the base class loaders in their dedicated articles which I guess are ClassLoader, ClassCollectionLoader and MapClassLoader.

We can then add articles for each of the class loader wrappers: ApcClassLoader, DebugClassLoader and XcacheClassLoader.

Any opinions on this?

[stof]

As it is deprecated, I think it definitely make sense to avoid documenting it. The ClassLoader should be preferred

[wouterj]

+1 do you start writing this, @xabbuh ? Otherwise I'll do it after my holiday.

[xabbuh]

I do. I think I can publish it to the end of the week for feedback.

[xabbuh]

At last, it took me longer than I expected. I'd appreciate any feedback on this.