unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Robert Weiner <rsw@gnu.org>
To: emacs-devel <emacs-devel@gnu.org>
Cc: Stephen Berman <stephen.berman@gmx.net>
Subject: Re: Emacs 24.0.94: With function argdesc bitstring, Elisp manual does not say how to get arg list
Date: Thu, 30 Jun 2016 12:30:21 -0400	[thread overview]
Message-ID: <CA+OMD9j7yF9ezJp7-XHVRDfu=wnfLzjjBh+yfriD_6G6JAhxQQ@mail.gmail.com> (raw)
In-Reply-To: <CA+OMD9hkVxVptH5Y_FyVKpHn7yDz++=DOY=1B_AxfnqdZ2tMow@mail.gmail.com>

On Thu, Jun 30, 2016 at 10:11 AM, Robert Weiner <rsw@gnu.org> wrote:
> Is there a Lisp function to extract the argument list of a byte-coded
> function when it uses the bitstring arg descriptor in its first
> element (see below for the Elisp manual doc on this)?

I see now through disassembly of such byte-coded functions that the
byte-compiler discards the actual names of the arguments and the
disassembler just outputs placeholders for them.  Why not preserve the
argument signature as is done for functions with a fixed number of
arguments?  In Lisp, we should be able to reason about compiled code
too, right?

Bob



  parent reply	other threads:[~2016-06-30 16:30 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
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 [this message]
2016-07-06 21:57   ` 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+OMD9j7yF9ezJp7-XHVRDfu=wnfLzjjBh+yfriD_6G6JAhxQQ@mail.gmail.com' \
    --to=rsw@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=rswgnu@gmail.com \
    --cc=stephen.berman@gmx.net \
    /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).