Re: Question about large objects

From:

=?iso-8859-1?q?Kirit_S=E6lensminde?= <kirit.saelensminde@gmail.com>

Newsgroups:

comp.lang.c++

Date:

20 Apr 2007 21:40:58 -0700

Message-ID:

<1177130458.741057.165190@y80g2000hsf.googlegroups.com>

On Apr 20, 10:53 pm, JoeC <enki...@yahoo.com> wrote:

I have been writing games and I also read about good programming
techniques. I tend to create large objects that do lots of things. A
good example I have is a unit object. The object controls and holds
everything a unit in my game is supposed to do. What are some some
cures for this kind of large object or are they OK because they
represent one thing. If not what are better ways to design objects
that behave the same way. Would it be better to use inheritance or
friends and where can I look to be able to do the same thing in a
better way?

Here is a unit from a completed game I created. The header file at
least to give an idea of one of my larger objects.

[snip huge class]

You're using the class more like a namespace here. Objects should be
cohesive, which is a word that takes a look of thinking about to
really understand. A simple definition is that they should do only one
thing and do that one thing well. The smaller the scope of the one
thing they do the better.

Look at http://c2.com/cgi/wiki?ClassicOoAntiPatterns and especially
http://c2.com/cgi/wiki?ClassesWithoutOo

K