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=-1.3 required=5.0 tests=BAYES_00,INVALID_MSGID autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,c5044d605ee95b02,start X-Google-Attributes: gid103376,public From: "Matthew Heaney" Subject: ANNOUNCE: Observing a Subject's Attributes article posted Date: 1999/09/12 Message-ID: <37dc4d0a@news1.prserv.net>#1/1 X-Deja-AN: 524271523 Content-transfer-encoding: 7bit Content-Type: text/plain; charset="US-ASCII" X-Complaints-To: abuse@prserv.net X-Trace: 13 Sep 1999 01:02:02 GMT, 129.37.213.5 Organization: Global Network Services - Remote Access Mail & News Services Mime-version: 1.0 Newsgroups: comp.lang.ada Date: 1999-09-12T00:00:00+00:00 List-Id: The article "Observing a Subject's Attributes" has been posted to the Ada95 patterns list. It appears under "September 1999" in the patterns archive. All the Ada95 source code is included in the message. Here's the introduction: In previous implementations of the Observer pattern, the observer would query the entire state of the subject during a notification, because it had no way of knowing which specific attribute had changed. Here, we vary the pattern so that the observer can observe each subject attribute individually, so it only has to display the attribute that has changed. You can subscribe to the Ada95 patterns list by sending the message (body) subscribe patterns to the ACM mailing list server. You can send comments and questions to the Ada95 patterns list, or to me directly. Matt