From: Kevin Rodgers <kevin.d.rodgers@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: elisp's cl package. Don't understand the notice about eval-when-compile
Date: Wed, 25 Mar 2009 20:53:28 -0600 [thread overview]
Message-ID: <gqeqmf$29i$1@ger.gmane.org> (raw)
In-Reply-To: <af7ab07a-f2ab-4640-af87-6ea6f6797c03@s12g2000prc.googlegroups.com>
Xah Lee wrote:
> in emacs lisp's CL package documentation “(info "(cl)Overview")”, it
> has this passage:
>
> *Please note:* the "CL" functions are not standard parts of the
> Emacs Lisp name space, so it is legitimate for users to define them
> with other, conflicting meanings. To avoid conflicting with those
> user
> activities, we have a policy that packages installed in Emacs must not
> load "CL" at run time. (It is ok for them to load "CL" at compile
> time
> only, with `eval-when-compile', and use the macros it provides.) If
> you are writing packages that you plan to distribute and invite
> widespread use for, you might want to observe the same rule.
>
> I don't quite understand it.
>
> If i distribute a package xyz.el, which calls
>
> (eval-when-compile (require 'cl))
>
> And, this package does not require users to byte-compile it. Then,
> how's the eval-when-compile solve the name conflict problem?
>
> does it imply that if you distribute a package using cl, it must be
> byte compiled eventually?
Of course, no library _must_ be compiled. But the unstated assumption
is that every library is byte-compiled because of the performance
benefits (during loading _and_ execution).
And if you load and execute a compiled library that uses CL macros (but
not CL functions) via eval-when-compile, then the obarray remains pure.
:-)
--
Kevin Rodgers
Denver, Colorado, USA
prev parent reply other threads:[~2009-03-26 2:53 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-25 3:02 elisp's cl package. Don't understand the notice about eval-when-compile Xah Lee
2009-03-25 4:42 ` Michael Ekstrand
2009-03-25 10:02 ` Thomas F. Burdick
2009-03-26 2:12 ` Xah Lee
2009-03-26 5:30 ` Jason Rumney
2009-03-26 13:15 ` Thomas F. Burdick
2009-04-01 1:01 ` Miles Bader
2009-03-26 8:58 ` Leo
2009-03-26 9:32 ` Juanma Barranquero
2009-03-26 12:37 ` Leo
2009-03-26 15:09 ` Samuel Wales
2009-03-26 20:09 ` Leo
2009-03-26 21:54 ` Lennart Borgman
2009-03-27 1:42 ` Kevin Rodgers
[not found] ` <mailman.4060.1238118196.31690.help-gnu-emacs@gnu.org>
2009-03-27 6:30 ` Xah Lee
2009-03-27 8:30 ` Kojak
2009-03-27 10:37 ` David Kastrup
2009-03-29 18:20 ` Eli Zaretskii
[not found] ` <mailman.4213.1238350954.31690.help-gnu-emacs@gnu.org>
[not found] ` <2f147e23-2e25-4cfb-885c-64d835993b12@y6g2000prf.googlegroups.com>
2009-03-30 20:03 ` B. T. Raven
2009-03-30 20:50 ` Lennart Borgman
2009-03-31 4:12 ` Xah Lee
2009-03-31 5:40 ` B. T. Raven
2009-03-31 9:50 ` Nikolaj Schumacher
2009-03-31 10:36 ` Alan Mackenzie
2009-03-26 2:53 ` Kevin Rodgers [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='gqeqmf$29i$1@ger.gmane.org' \
--to=kevin.d.rodgers@gmail.com \
--cc=help-gnu-emacs@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.