changeset 40590:e9ca70d27e37

Explain when not to use CL.
author Richard M. Stallman <rms@gnu.org>
date Wed, 31 Oct 2001 22:00:17 +0000
parents c44c1b0bdf92
children a8c2103fca6f
files man/cl.texi
diffstat 1 files changed, 10 insertions(+), 0 deletions(-) [+]
line wrap: on
line diff
--- a/man/cl.texi	Wed Oct 31 21:59:42 2001 +0000
+++ b/man/cl.texi	Wed Oct 31 22:00:17 2001 +0000
@@ -121,6 +121,16 @@
 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: