From ... Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!newsfeeds.belnet.be!news.belnet.be!news2.kpn.net!news.kpn.net!nslave.kpnqwest.net!nloc.kpnqwest.net!nmaster.kpnqwest.net!nreader1.kpnqwest.net.POSTED!not-for-mail Newsgroups: comp.lang.lisp Subject: Re: Aliasing slots References: Mail-Copies-To: never From: Erik Naggum Message-ID: <3217576858921853@naggum.net> Organization: Naggum Software, Oslo, Norway Lines: 22 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.1 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 17 Dec 2001 11:21:00 GMT X-Complaints-To: newsmaster@KPNQwest.no X-Trace: nreader1.kpnqwest.net 1008588060 193.71.66.49 (Mon, 17 Dec 2001 12:21:00 MET) NNTP-Posting-Date: Mon, 17 Dec 2001 12:21:00 MET Xref: archiver1.google.com comp.lang.lisp:22595 * james@unlambda.com (James A. Crippen) | (defclass pname-mixin () | ((pname :type string | :initarg :pname | :accessor pname-of))) | | (defclass foo (name-mixin) | ((name :type string | :initarg :name | :accessor name-of))) If these are the same slot, just use the same slot name. However, what is the point in using the mixin superclass if you repeat the slot information in the subclass? /// -- The past is not more important than the future, despite what your culture has taught you. Your future observations, conclusions, and beliefs are more important to you than those in your past ever will be. The world is changing so fast the balance between the past and the future has shifted.