Resetting Objects vs. Constructing New Objects

Posted by byronh on Stack Overflow See other posts from Stack Overflow or by byronh
Published on 2010-04-03T20:08:30Z Indexed on 2010/04/03 20:13 UTC
Read the original article Hit count: 274

Filed under:
|
|
|
|

Is it considered better practice and/or more efficient to create a 'reset' function for a particular object that clears/defaults all the necessary member variables to allow for further operations, or to simply construct a new object from outside?

I've seen both methods employed a lot, but I can't decide which one is better. Of course, for classes that represent database connections, you'd have to use a reset method rather than constructing a new one resulting in needless connecting/disconnecting, but I'm talking more in terms of abstraction classes.

Can anyone give me some real-world examples of when to use each method? In my particular case I'm thinking mostly in terms of ORM or the Model in MVC. For example, if I would want to retrieve a bunch of database objects for display and modify them in one operation.

© Stack Overflow or respective owner

Related posts about oop

Related posts about best-practices