small base class

From: Guybrush Treepwood (schemer_at_hotmail.com)
Date: 01/11/05 

Date: Tue, 11 Jan 2005 07:12:28 +0100

I'm programming a postnetwork simulation. There are Offices and Links
between them, postmessages get send through to another office whenever
there still is no link between the office and the recipient. So the
recipients are regular people who can receive a message, but from where you
can't send one. The offices and links are checked by a discrete event
simulator to see if they have anything to send.

Is thought something about this would do as inheritance hierarchy:

abstract base class: Receiver

abstract class ControlableObject inherits from Receiver
Person inherits from Receiver

Office inherits from ControlableObject
Link inherits from ControlableObject

My question now is, the abstract base class Receiver has only 1 method,
receive. This makes me wonder, is this a good design?

Relevant Pages

  • Re: small base class
    ... > I'm programming a postnetwork simulation. ... > abstract class ControlableObject inherits from Receiver ... the abstract base class Receiver has only 1 ...
    (comp.object)
  • Re: small base class
    ... > there still is no link between the office and the recipient. ... > abstract class ControlableObject inherits from Receiver ...
    (comp.object)
  • Re: Quarks
    ... Inherits from Object ... no ancestors. ... So it matters what it means that "methods in the receiver" will be listed. ... Sending .methodswill just give you an empty array. ...
    (comp.lang.ruby)