Xref: utzoo comp.object:262 comp.lang.lisp:2288 comp.sys.mac:40838 Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!rutgers!tut.cis.ohio-state.edu!gem.mps.ohio-state.edu!uwm.edu!mrsvr.UUCP!positron.uucp!hallett From: hallett@positron.uucp (Jeff Hallett x5163 ) Newsgroups: comp.object,comp.lang.lisp,comp.sys.mac Subject: Re: Static v. Dynamic Class Structure Message-ID: <1292@mrsvr.UUCP> Date: 24 Oct 89 15:28:58 GMT References: Sender: news@mrsvr.UUCP Reply-To: hallett@gemed.ge.com (Jeffrey A. Hallett (414) 548-5163) Followup-To: comp.object Organization: GE Medical Systems, Milwaukee, WI Lines: 28 In article alms@cambridge.apple.com (Andrew L. M. Shalit) writes: > >I'm surprised no one has responded to this yet. CLOS doesn't >assume a static system. Classes can be redefined, and there >is a full protocol for updating existing instances. This is >possible because object system support exists at run time, not >just at compile time. I cross-post this because people may be able to answer the follow-up that are on different groups. I am interested in seeing CLOS over on the Mac under (formerly) Allegro Common Lisp. I am under the impression that CLOS itself is freely distributed (various implementations cost $, but CLOS itself, like TeX, is free). Has anyone had any luck porting CLOS to the Mac and possibly expanding the class database to include ToolBox elements (windows, menus, etc)? Thanks -- Jeffrey A. Hallett, PET Software Engineering GE Medical Systems, W641, PO Box 414, Milwaukee, WI 53201 (414) 548-5163 : EMAIL - hallett@gemed.ge.com "Your logic was impeccable Captain. We are in grave danger."