Run another controller's method

[eluser]John Fuller[/eluser]
I don't get it.

I have a model for the blog and another for comments (as well as more models for the admin versions of each.) All the controller does is make the calls to all the models needed, loads up the array and spews everything out into the view page. That is all the controller is, a middle man. The real action is going on in the models.

There might be a little bit of overlap between two controllers doing much the same stuff but why be so hardcore about not reusing code? For instance, I have a blog controller and an archive controller. The blog just shows entries and the number of comments. The archives controller shows a single entry, all the comments for that entry and a comment form. The two controllers are similar but not exactly the same.

So in Sam's example, why not do (in my uber pseudocode)

[call model(blog), call model(comments)] => controller => view => collect underpants => ? => profit!