Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!peirce.cis.ohio-state.edu!welch From: welch@peirce.cis.ohio-state.edu (Arun Welch) Newsgroups: comp.lang.lisp Subject: Re: CLOS: is it OOP? Message-ID: Date: 14 Sep 89 14:01:41 GMT References: <19582@mimsy.UUCP> Sender: news@tut.cis.ohio-state.edu Distribution: usa Organization: OSU-LAIR Lines: 18 In-reply-to: folta@tove.umd.edu's message of 14 Sep 89 00:21:12 GMT > and I have ordered Xerox's CommonLOOPS Huh? CommonLoops was an early name for PCL (Portable Common Loops), which has been the primary implementation engine for CLOS. Someone's pulling your leg. Anyway, I've used both PCL and Loops extensively, and can say that CLOS *is* an OOPS, just in a different style than the other OOPS, where method calls were active sends. If you're really hung up on using send, it's pretty trivial to define a macro to dispatch the appropriate method. ...arun ---------------------------------------------------------------------------- Arun Welch Lisp Systems Programmer, Lab for AI Research, Ohio State University welch@tut.cis.ohio-state.edu