Xref: utzoo comp.lang.misc:7160 comp.object:2959 Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!samsung!uunet!cimshop!davidm From: cimshop!davidm@uunet.UU.NET (David S. Masterson) Newsgroups: comp.lang.misc,comp.object Subject: Re: CHALLENGE: heterogeneous collections Message-ID: Date: 29 Mar 91 03:13:55 GMT References: <1991Mar25.220525.11087@leland.Stanford.EDU> <1991Mar26.101051.29527@irisa.fr> Sender: davidm@cimshop.UUCP Distribution: comp Organization: Consilium Inc., Mountain View, California Lines: 25 In-reply-to: boissier@irisa.fr's message of 26 Mar 91 10:10:51 GMT >>>>> On 26 Mar 91 10:10:51 GMT, boissier@irisa.fr (franck boissiere) said: Franck> There is at least one kind of system which must allow heterogeneous Franck> collections. It is often called Open System. Is these systems the Franck> person who writes the kernel do not know anything about what objects Franck> will be used by the persons who will extend the system. What message would this OpenSystem send to the objects that it deals with? What do those messages have in common? If they have nothing in common, then how does the OpenSystem even know what messages to send to these collections of objects? Franck> Another exemple is for debugging, where you might collect any kind Franck> of objects. Wouldn't it all be of type DebugInformation? Therefore, same questions apply. Next contestant. (I like that phrase, Chip :-) -- ==================================================================== David Masterson Consilium, Inc. (415) 691-6311 640 Clyde Ct. uunet!cimshop!davidm Mtn. View, CA 94043 ==================================================================== "If someone thinks they know what I said, then I didn't say it!"