From: Robert Weiner <rsw@gnu.org>
To: Richard Stallman <rms@gnu.org>
Cc: 23873@debbugs.gnu.org, emacs-devel <emacs-devel@gnu.org>
Subject: Re: bug#23873: Emacs 24.0.94: With function argdesc bitstring, Elisp manual does not say how to get arg list
Date: Fri, 1 Jul 2016 08:14:41 -0400 [thread overview]
Message-ID: <CA+OMD9g+U-V0227AvqtP+tc3QxvjVeYCxDgFDfgPAvXZmeb3Bg@mail.gmail.com> (raw)
In-Reply-To: <E1bIlFu-0002vg-JI@fencepost.gnu.org>
On Thu, Jun 30, 2016 at 7:20 PM, Richard Stallman <rms@gnu.org> wrote:
> > For years, XEmacs has had functions for accessing parts of
> > byte-compiled code. It would be great if Emacs had some equivalents.
>
> There is nothing wrong with this, but it would be clutter.
> Why do you want them?
In a few places, Hyperbole uses its own function to overload existing
functions with its own and needs access to the function's argument
signature to do this. For reasons of backward compatibility,
Hyperbole has not used defadvice. In another case, we want to know if
a function's signature has changed for a conditional dispatch.
> Perhaps they can be defsubrs defined in a file that you'd load
> at compile time.
That would be fine with me. I would be willing to be a tester and as
a first step need only the argument signature extraction routine.
Is anyone interested in implementing this?
Bob
next prev parent reply other threads:[~2016-07-01 12:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <871t3edfd9.fsf@gmx.net>
2016-06-30 14:11 ` Emacs 24.0.94: With function argdesc bitstring, Elisp manual does not say how to get arg list Robert Weiner
2016-06-30 14:51 ` Drew Adams
2016-06-30 15:46 ` bug#23873: " Robert Weiner
2016-06-30 23:20 ` Richard Stallman
2016-07-01 12:14 ` Robert Weiner [this message]
2016-07-01 14:01 ` Drew Adams
2016-07-01 22:04 ` Richard Stallman
2016-07-01 22:43 ` Robert Weiner
2016-06-30 16:30 ` Robert Weiner
2016-07-06 21:57 ` bug#23873: " Robert Weiner
2016-07-06 23:32 ` Drew Adams
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=CA+OMD9g+U-V0227AvqtP+tc3QxvjVeYCxDgFDfgPAvXZmeb3Bg@mail.gmail.com \
--to=rsw@gnu.org \
--cc=23873@debbugs.gnu.org \
--cc=emacs-devel@gnu.org \
--cc=rms@gnu.org \
--cc=rswgnu@gmail.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.
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).