Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!uwm.edu!cs.utexas.edu!rutgers!njin!princeton!phoenix!eliot
From: eliot@phoenix.Princeton.EDU (Eliot Handelman)
Newsgroups: comp.lang.lisp
Subject: Re: updating random slots in (say) defstruct
Message-ID: <12955@phoenix.Princeton.EDU>
Date: 16 Jan 90 02:59:28 GMT
References: <18963@bellcore.bellcore.com> <Jan.15.12.33.43.1990.625@atanasoff.rutgers.edu>
Reply-To: eliot@phoenix.Princeton.EDU (Eliot Handelman)
Organization: Princeton University, NJ
Lines: 17

In article <Jan.15.12.33.43.1990.625@atanasoff.rutgers.edu> lou@atanasoff.rutgers.edu (Lou Steinberg) writes:
;In article <18963@bellcore.bellcore.com> pc@flash.bellcore.com writes:
;
;>                                                    But what i want to
;> do, is define a SETFable function created with (INTERN (string-append
;> <defstruct-name> "-" <slot-name>)).  Perhaps i really have to throw the
;> whole expression i've consed up to EVAL.  But that really is a bit
;> gross.

I ran into a similar problem, compounded by the fact that I wanted to
define a few extra options to defstruct, so I wound up writing a 
defstruct preprocessor. I save any values that interest me, such as the
names of all the accessors. 

Zetalisp had the defstruct-description structure to access basic information,
like the names of all the slots, the names of the accessors to each slot, etc.
Too bad CL dropped it. Why was that? Anything to do with metaobjects?