Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!apple!ames!ncar!boulder!gore!jacob
From: jacob@gore.com (Jacob Gore)
Newsgroups: comp.lang.c++
Subject: Re: Objectifying incoming messages?
Message-ID: <110003@gore.com>
Date: 5 Aug 89 16:29:30 GMT
References: <444@cimshop.UUCP>
Reply-To: jacob@gore.com (Jacob Gore)
Organization: Gore Enterprises
Lines: 18

/ comp.lang.c++ / eberard@ajpo.sei.cmu.edu (Edward Berard) / Aug  4, 1989 /
> Our course of action is simple. We first remove the composite
> operation (i.e., "Display") from the interface of the counter class
> and replace it with a selector operation which returns the current
> value of a counter object. We have now decoupled the counter class
> from the output object class using selector decoupling. 

This appears to imply that there is an intermediate representation for the
object's value that can be returned by the source object's selector and the
destination object's constructor.  In this case, it's easy: a number object
can represent the counter's value.

What do you do if the value is quite complex?  Encode it in some
agreed-upon representation, such as in a structure or a character string?

Jacob
--
Jacob Gore	Jacob@Gore.Com		{nucsrl,boulder}!gore!jacob