public inbox for guile-emacs@sourceware.org
 help / color / mirror / Atom feed
From: Kalle Olavi Niemitalo <tosi@stekt.oulu.fi>
To: guile-emacs@sourceware.cygnus.com
Subject: Re: scheme-describe-symbol
Date: Sat, 29 Apr 2000 11:37:00 -0000	[thread overview]
Message-ID: <877ldgrc8y.fsf@PC486.Niemitalo.LAN> (raw)
In-Reply-To: <m31z3p6zk5.fsf@kei.cwru.edu>

Keisuke Nishida <kxn30@po.cwru.edu> writes:

> GOOPS methods could be described specially, like:
> 
> ----------------------------------------
> `+' is a method.
> 
> (+ <integer> <integer>)
> 
>   ....

OW!  I spent the last few hours implementing a generic
`describe-object' with methods for procedures, macros and generic
functions... until I noticed GOOPS has had the functionality all
the time:

guile> (use-modules (oop goops describe))
guile> (describe describe)
describe is a generic function. It's an instance of <generic>.
Methods defined for describe
    Method #<<method> (<method> . <top>) 402b92b0>
        Specializers: <method> <top>
    Method #<<method> (<generic>) 402ad0b8>
        Specializers: <generic>
    Method #<<method> (<class>) 4028b758>
        Specializers: <class>
    Method #<<method> (<object>) 40279b18>
        Specializers: <object>
    Method #<<method> (<procedure>) 401cda48>
        Specializers: <procedure>
    Method #<<method> (<top>) 402e4890>
        Specializers: <top>

I guess I'll use that instead... except `describe' doesn't show
documentation strings.  What would be the best way to add them?

  parent reply	other threads:[~2000-04-29 11:37 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-04-29  1:25 scheme-describe-symbol Kalle Olavi Niemitalo
2000-04-29  2:12 ` scheme-describe-symbol Keisuke Nishida
2000-04-29 11:37   ` scheme-describe-symbol Kalle Olavi Niemitalo
2000-04-29 12:22     ` scheme-describe-symbol Keisuke Nishida
2000-04-30  6:57       ` scheme-describe-symbol Kalle Olavi Niemitalo
2000-05-01 18:16         ` scheme-describe-symbol Keisuke Nishida
2000-04-29 11:37   ` Kalle Olavi Niemitalo [this message]
2000-04-29 12:42     ` scheme-describe-symbol Keisuke Nishida

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=877ldgrc8y.fsf@PC486.Niemitalo.LAN \
    --to=tosi@stekt.oulu.fi \
    --cc=guile-emacs@sourceware.cygnus.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).