🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: comp.lang.clos
Article #330

Re: Retrieving documentation of slots?

#330
From: Barry Margolin
Date: Tue, 13 Oct 1992 19:20
23 lines
1556 bytes
In article <1992Oct13.181308.24194@umbc3.umbc.edu> cs631114@umbc8.umbc.edu (cs631114) writes:
>Hmm, I finally got around to trying to use doc strings on slots, and much
>to my embarrassment realized I didn't know how to retrieve them! Assumedly
>I am overloooking the obvious. Hints, anyone?

No, you're not overlooking anything.  As it says in the Notes section of
the dpANS description of DOCUMENTATION:

    This standard prescribes no means to retrieve the \term{documentation
    strings} for individual slots specified in a \macref{defclass} form,
    but \term{implementations} might still provide debugging tools and/or
    programming language extensions which manipulate this information.
    Implementors wishing to provide such support are encouraged to consult
    the \term{Metaobject Protocol} for suggestions about how this might be
    done.

In most implementations you should be able to get the documentation strings
with the MOP, presumably using an accessor on the slot-description object.
-- 
Barry Margolin
System Manager, Thinking Machines Corp.

barmar@think.com          {uunet,harvard}!think!barmar
Technical Details
Message-ID: <1bf7hrINNg9g@early-bird.think.com>
Path: arc1-ca.pugleaf.net!sparky!uunet!think.com!barmar
References: <1992Oct13.181308.24194@umbc3.umbc.edu>

Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!sparky!uunet!think.com!barmar
From: barmar@think.com (Barry Margolin)
Newsgroups: comp.lang.clos
Subject: Re: Retrieving documentation of slots?
Date: 13 Oct 1992 19:20:27 GMT
Organization: Thinking Machines Corporation, Cambridge MA, USA
Lines: 23
Message-ID: <1bf7hrINNg9g@early-bird.think.com>
References: <1992Oct13.181308.24194@umbc3.umbc.edu>
NNTP-Posting-Host: telecaster.think.com