From: Ted Zlatanov <tzz@lifelogs.com>
To: emacs-devel@gnu.org
Subject: Re: ELisp function prototypes and local function name
Date: Wed, 06 Apr 2011 10:58:00 -0500 [thread overview]
Message-ID: <87k4f7pe2f.fsf@lifelogs.com> (raw)
In-Reply-To: pkn4o6bh0fe.fsf@this.is.really.invalid
On Wed, 06 Apr 2011 17:19:49 +0200 Robert Pluim <rpluim@gmail.com> wrote:
RP> Ted Zlatanov <tzz@lifelogs.com> writes:
>> I often find myself needing to know the prototype of a function I'm
>> calling dynamically. Is there a way to get that? The ELisp reference
>> manual doesn't have the info AFAICT.
RP> You mean like eldoc-mode?
Oh yes, I didn't think to check there. It looks like that calls the
following (example with `mapc'):
(help-split-fundoc (documentation 'mapc t) 'mapc)
That seems nasty, taking text documentation and splitting it back to get
the function arguments. Is that really the only way to get back the
prototype? It seems like `eldoc-get-fnsym-args-string' should be able
to do something simpler.
The interpreter knows how many arguments a function expects and signals
an error if the count is incorrect. Can that be used instead of the
above?
Ted
next prev parent reply other threads:[~2011-04-06 15:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-06 13:36 ELisp function prototypes and local function name Ted Zlatanov
2011-04-06 15:19 ` Robert Pluim
2011-04-06 15:58 ` Ted Zlatanov [this message]
2011-04-07 0:25 ` Stephen J. Turnbull
2011-04-07 2:27 ` Ted Zlatanov
2011-04-07 3:27 ` Stephen J. Turnbull
2011-04-07 3:55 ` Jambunathan K
2011-04-07 5:43 ` Stephen J. Turnbull
2011-04-07 20:51 ` Ted Zlatanov
2011-04-08 4:01 ` Stephen J. Turnbull
2011-04-08 5:43 ` Ted Zlatanov
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87k4f7pe2f.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--cc=emacs-devel@gnu.org \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).