Posted by Sanders Kaufman on 07/25/07 04:57

ZeldorBlat wrote:

> Because you move don't duplicate the functionality -- you move it to
> it's own method and call that from the constructor. That way you
> don't need to call the constructor to reset things, and you don't need
> to duplicate any code. That's what we've been trying to say all along
> -- but you haven't seemed to have caught on.

Oh, I get it.
I just don't see a reason to do it that way.

In fact - that particular way actually seems even MORE unnecessarily
complex than the one the other guy provided where my "init()" function
would call the constructor.

In your case, every time my object is initialized, it would make TWO
function calls, instead of one - one to the constructor, and one to the
init().

That violates a core design principle - that it be very scalable; and
that means that it must not use resources unnecessarily.

[Back to original message]