From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: ***
X-Spam-Status: No, score=3.8 required=5.0 tests=BAYES_00,FREEMAIL_FROM,
	INVALID_MSGID,RATWARE_MS_HASH,RATWARE_OUTLOOK_NONAME autolearn=no
	autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: fac41,fb2e75ca89362493
X-Google-Attributes: gidfac41,public
X-Google-Thread: 109fba,fb2e75ca89362493
X-Google-Attributes: gid109fba,public
X-Google-Thread: 103376,fb2e75ca89362493
X-Google-Attributes: gid103376,public
X-Google-Thread: 114809,fb2e75ca89362493
X-Google-Attributes: gid114809,public
From: "Jim shaw" <James_P_Shaw@msn.com>
Subject: Re: Conception problem
Date: 1997/05/30
Message-ID: <01bc6c26$4e1c0ef0$ab526478@jims_nt_1>#1/1
X-Deja-AN: 244962497
References: <01bc6b91$54b26a60$d19ecec2@beta>
Organization: Corel Corporation
Newsgroups: comp.lang.ada,comp.lang.c++,comp.lang.eiffel,comp.lang.smalltalk
Date: 1997-05-30T00:00:00+00:00
List-Id: <comp.lang.ada>


A better solution would be to implement the Observer design pattern (Design
Patterns, by Gamma et.al.). Just a quick blurb on this pattern (please see
book for more detail):

Essentially all objects of class type B, would keep a list of "subscribed"
objects to notify when an event of interest occurs. When a particular event
(of your own choosing) occurs, the object simply "notifies" all subscribed
objects of this event (i.e. send a message to that object).


Nicolas Gautier <GautierN@sofreavia.fr> wrote in article
<01bc6b91$54b26a60$d19ecec2@beta>...
> Hello,
> Sorry if this mail is a little bit long. This is a question about what is
> the best 
> way to handle lists where modifications of one element can trigger
> modifications
> on other elements of the list.
> 


Ciao!
Jim Shaw