From: Keisuke Nishida <kxn30@po.cwru.edu>
To: guile-emacs@sourceware.cygnus.com
Subject: Re: scheme-describe-symbol
Date: Sat, 29 Apr 2000 02:12:00 -0000 [thread overview]
Message-ID: <m31z3p6zk5.fsf@kei.cwru.edu> (raw)
In-Reply-To: <87zoqdgvp7.fsf@PC486.Niemitalo.LAN>
Kalle Olavi Niemitalo <tosi@ees2.oulu.fi> writes:
> > ** Write scheme-describe-symbol and scheme-describe-object.
> >
> > scheme-describe-symbol describes a symbol literally.
> > scheme-describe-object describes the object associated with a symbol.
>
> What exactly would scheme-describe-symbol tell the user about the
> symbol, other than its name?
>
> How does scheme-describe-object choose the module where it takes
> the definition of the symbol? (Common Lisp has different symbols
> in different packages... Guile doesn't.)
I haven't thought enough about this yet, but I think there are two
cases where we want to use scheme-describe-*.
1. Find documentation by name.
Guile has documentation in guile-procedures.txt. We have to search
this file by procedure names.
2. Find documentation by object.
An extreme example:
(define + -)
(+ 1 2)
In this case, we may want to find the documentation of `-' instead of
that of `+'. We also want to describe slot information if the object
is a GOOPS object.
We could combine these two functions into one command, though.
The module can be decided by searching "(define-module ..." in the
current buffer, as scheme-eval-* does.
GOOPS methods could be described specially, like:
----------------------------------------
`+' is a method.
(+ <integer> <integer>)
....
(+ <real> <real>)
....
----------------------------------------
There are lots of things to do...
-- Kei
next prev parent reply other threads:[~2000-04-29 2:12 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 ` Keisuke Nishida [this message]
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 ` scheme-describe-symbol Kalle Olavi Niemitalo
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=m31z3p6zk5.fsf@kei.cwru.edu \
--to=kxn30@po.cwru.edu \
--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).