MVC frameworks, should models resemble a 'module'-like structure?

I'm in the early stages of building a website using CodeIgniter, a PHP MVC framework. My models are, so far, fairly simple, yet I'm already doubting my coding approach. Is it a bad idea to let models use eachother? While 开发者_如何学Pythonit certainly reduces the amount of code needed, it also raises a strong dependency on outside code within each model method. Is this okay? Or does the methods need a more 'module' approach where they just work, independent of other methods?

Thanks for your time.

---

In theory, models should be grouped together into independent modules. You should then be able to move that module from CodeIgniter app to CodeIgniter app and it should work with little to no modification.

So it's OK for models to use each other. A model should represent a real-world object, and real-world objects rely on each other too!

---

Yea There is 2 ways to do it how ever,

There is the model call (Instantiate) the new object its self

Or you can have your controller call (Instantiate) the object and pass it to your model

ether works but my personal preference to do the first