From: John Paul Wallington <jpw@pobox.com>
To: esr@thyrsus.com
Cc: Glenn Morris <rgm@gnu.org>, emacs-devel@gnu.org, esr@snark.thyrsus.com
Subject: Re: Some vc-dispatcher nitpicks
Date: Sat, 17 May 2008 11:42:28 +0100 [thread overview]
Message-ID: <E2D404D7-4600-41CE-B3D8-418B8BF883D9@pobox.com> (raw)
In-Reply-To: <20080516220831.GC23205@thyrsus.com>
On 16 May 2008, at 23:08, Eric S. Raymond wrote:
> John Paul Wallington <jpw@pobox.com>:
>> `gensym' is a function rather than a macro and it apparently doesn't
>> have a corresponding compiler macro. Use or loading of cl at
>> runtime by
>> packages that are installed in the Emacs sources is verboten.
>
> Hmmm...can anyone explain why that is? It should be docunted
> somewhere.
It's policy. It is documented in the elisp manual; see (elisp) Coding
Conventions:
* Please don't require the `cl' package of Common Lisp extensions at
run time. Use of this package is optional, and it is not part of
the standard Emacs namespace. If your package loads `cl' at run
time, that could cause name clashes for users who don't use that
package.
However, there is no problem with using the `cl' package at
compile time, with `(eval-when-compile (require 'cl))'. That's
sufficient for using the macros in the `cl' package, because the
compiler expands them before generating the byte-code.
>> Is it okay to install the following patch?
>
> Yes, that looks good. Thanks. It might be possible to remove the
> eval-compile
> of cl, as well, once you've done this; you'd be doing me a favor if
> you checked.
Checked it. Doesn't work, though I mistakenly thought it did. O_o
prev parent reply other threads:[~2008-05-17 10:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-16 18:25 Some vc-dispatcher nitpicks Glenn Morris
2008-05-16 19:55 ` Eric S. Raymond
2008-05-16 21:11 ` John Paul Wallington
2008-05-16 22:08 ` Eric S. Raymond
2008-05-17 10:42 ` John Paul Wallington [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E2D404D7-4600-41CE-B3D8-418B8BF883D9@pobox.com \
--to=jpw@pobox.com \
--cc=emacs-devel@gnu.org \
--cc=esr@snark.thyrsus.com \
--cc=esr@thyrsus.com \
--cc=rgm@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.