🚀 go-pugleaf

In article <4565t8$u5q@hopi.gate.net>, Ken Walter writes:

> Nelson Yu (nelson@scapa.cs.ualberta.ca) wrote:
> : 4) A nice class hierarchy(i.e everything is derived from object)
>
> Very argumentative!  Deep trees result in almost monolithic systems
> that are hard to change.

This only brings difficulties when people introduce into an "Object" root
class, behaviour that is specific to particular kinds of objects.  There
is one school of thought that says that the only kind of behaviour that
can possibly be relevant to *ALL* objects without exception is the ability
to be referenced, which leads to the creation of a top-level Object class
that everyone inherits but which is purely abstract, state-free, and with
no specific behaviour other than for simple creation and destruction.

That sort of structure does not introduce any real maintenance problems.
It doesn't actually do anything, other than allow generic references to
objects of any class in those cases where this can be helpful.

-- 
###########  Dr. Rich Artym  ================  PGP public key available
# galacta #  Internet: rich@galacta.demon.co.uk     DNS 158.152.156.137
# ->demon #            rich@mail.g7exm[.uk].ampr.org   DNS 44.131.164.1
# ->ampr  #  NTS/BBS : g7exm@gb7msw.#33.gbr.eu
# ->nexus #  Fun     : Unix, X, TCP/IP, OSI, kernel, O-O, C++, Soft/Eng
# ->NTS   #  More fun: Regional IP Coordinator Hertfordshire + N.London
###########  Q'Quote : "Object type is a detail of its implementation."