🚀 go-pugleaf

Robert C. Martin (rmartin@oma.com) wrote:
:...
: Certainly there are costs.  You have named them.  Your design is
: getting more complicated.  (Interesting isn't it.  When the design
: becomes more complex, the code gets simpler.  Complex problems require
: complex expressions.)  Your makefiles are more complex.  You need some
: way to manage all the source files.
: 
: Now ask yourself if there is a net gain.  Is the system overall easier
: to deal with?  

In most cases where the complexity of a C++, or other oopl, project has
been previously addressed, the solution can be made into a library -
static or dynamic - which subsequent programmers can use with less
complexity.  This is a major part of the component and object reuse
motivation.  So that the design of similar future projects in the domain
are not generally as visibly (code weight wise) complex.

Elliott

      [ Articles to moderate: mailto:c++-submit@netlab.cs.rpi.edu ]
      [  Read the C++ FAQ: http://www.connobj.com/cpp/cppfaq.htm  ]
      [  Moderation policy: http://www.connobj.com/cpp/guide.htm  ]
      [      Comments? mailto:c++-request@netlab.cs.rpi.edu       ]