From: Richard M. Stallman <rms@gnu.org>
Date: Wed, 31 Oct 2001 22:00:17 +0000 (+0000)
Subject: Explain when not to use CL.
X-Git-Tag: ttn-vms-21-2-B4~18932
X-Git-Url: http://git.eshelyaron.com/gitweb/?a=commitdiff_plain;h=a0e204da2c1a211d8534b48f199f93d47b920421;p=emacs.git

Explain when not to use CL.
---

diff --git a/man/cl.texi b/man/cl.texi
index 1d76bac5438..1597119ea4c 100644
--- a/man/cl.texi
+++ b/man/cl.texi
@@ -121,6 +121,16 @@ control structures to Emacs Lisp.  While not a 100% complete
 implementation of Common Lisp, @dfn{CL} adds enough functionality
 to make Emacs Lisp programming significantly more convenient.
 
+@strong{Please note:} the @dfn{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 @dfn{CL} at run time.  (It is ok for them to load
+@dfn{CL} at compile time only, with @code{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.
+
 Some Common Lisp features have been omitted from this package
 for various reasons: