From: Miles Bader <miles@gnu.org>
Subject: Re: CL compatibility question
Date: 07 May 2004 07:02:46 +0900 [thread overview]
Message-ID: <87n04lb4e1.fsf@tc-1-100.kawasaki.gol.ne.jp> (raw)
In-Reply-To: mailman.3786.1083877034.1061.help-gnu-emacs@gnu.org
Joe Corneli <jcorneli@math.utexas.edu> writes:
> (defmacro defbashfun (name lambda &body body)
> `(defun ,name (&rest $@)
> (apply (lambda ,lambda ,@body) $@)))
...
> Why is this? Are there plans that would change this behavior in the
> future?
Use &rest, not &body (in CL, &body is really just &rest with a hint to
the pretty-printer).
-Miles
--
[|nurgle|] ddt- demonic? so quake will have an evil kinda setting? one that
will make every christian in the world foamm at the mouth?
[iddt] nurg, that's the goal
next prev parent reply other threads:[~2004-05-06 22:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.3786.1083877034.1061.help-gnu-emacs@gnu.org>
2004-05-06 21:53 ` CL compatibility question Lawrence Mitchell
2004-05-06 21:56 ` Stefan Monnier
2004-05-06 22:02 ` Miles Bader [this message]
2004-05-06 19:36 Joe Corneli
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=87n04lb4e1.fsf@tc-1-100.kawasaki.gol.ne.jp \
--to=miles@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.
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).