unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: RFC: `macro-eval'
Date: Thu, 31 Aug 2006 03:33:34 -0400	[thread overview]
Message-ID: <E1GIh3O-0008Hd-Oj@fencepost.gnu.org> (raw)
In-Reply-To: <43976.128.165.123.18.1156957903.squirrel@webmail.lanl.gov> (herring@lanl.gov)

    I wrote a macro to automatically generate the boilerplate "delayed
    evaluation with uninterned symbol" code needed in many macros (and
    described at (elisp)Surprising Local Vars), which I present for comment. 

Actually we recently decided to stop using that method for two
important macros, dotimes and dolist, because it turns out to be
rather wasteful to generate all those symbols.  We concluded that it
is better, overall, to use an interned symbol so that only one symbol
would be needed.  We gave the interned symbol a name that users will
tend not to use.

Maybe that means we should change the recommendations in the Lisp
Manual.  However, for other macros that are used less often, the
recommendation there may still be best.

In many other Lisp implementations the compiler would get rid of such
variables, so the recommended technique costs nothing.  But the Emacs
Lisp byte compiler can't do that, because Emacs bytecode has no
anonymous stack slots.

    As far as my testing shows, it works both in interpreted and compiled
    environments, with the one caveat that, as it uses `progv', it both
    requires the cl library at runtime

That is a fatal flaw for this implementation.

  reply	other threads:[~2006-08-31  7:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-30 17:11 RFC: `macro-eval' Stuart D. Herring
2006-08-31  7:33 ` Richard Stallman [this message]
2006-08-31  7:47   ` David Kastrup
2006-08-31 22:57     ` Richard Stallman

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=E1GIh3O-0008Hd-Oj@fencepost.gnu.org \
    --to=rms@gnu.org \
    --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).