Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!linac!att!cbfsb!cbnewsc!cbnewsc!lgm From: lgm@cbnewsc.ATT.COM (lawrence.g.mayka) Newsgroups: comp.lang.lisp Subject: Re: SETQ vs SETF (was Re: Question about INTERN) Message-ID: Date: 12 Feb 91 15:37:33 GMT References: <1991Jan31.180524.21828@Think.COM> <4094@skye.ed.ac.uk> Sender: lgm@cbnewsc.att.com (lawrence.g.mayka) Organization: AT&T Bell Laboratories Lines: 20 In-Reply-To: jeff@aiai.ed.ac.uk's message of 11 Feb 91 17:50:02 GMT In article <4094@skye.ed.ac.uk> jeff@aiai.ed.ac.uk (Jeff Dalton) writes: or else vary from implementation to implementation. For example, there's no portable way to find out what slots a defstruct has even though the information ust be there for printing. This means In draft ANSI Common Lisp, the semi-portable way (i.e., via metaobject accessors agreed upon by major CL vendors) is (MAPCAR #'CLOS:SLOT-DEFINITION-NAME (CLOS:CLASS-SLOTS (FIND-CLASS 'STRUCTURE-TYPE-NAME))) for a structure type called STRUCTURE-TYPE-NAME. Lawrence G. Mayka AT&T Bell Laboratories lgm@iexist.att.com Standard disclaimer.