Sam Hennessy has continued his series looking at dependency injection in PHP with part one (technically the second part, here's part 0) - what he wants out of a dependency injection framework.

This article is part of a series where I will go into great detail about Dependency Injection (DI) and how it applies to PHP. I will layout exactly how I think DI should be used in PHP with the creation of a new code project as the result.

He has made a list of things that he's want a DI framework to do for him including:

• functionality that helps to keep things manageable
• making it all testable
• make a reduction in the need for "boilerplate code"
• work completely standalone if need be