emacs-diffs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Emacs-diffs] /srv/bzr/emacs/trunk r110614: * doc/lispref/tips.texi (Cod


From: Glenn Morris
Subject: [Emacs-diffs] /srv/bzr/emacs/trunk r110614: * doc/lispref/tips.texi (Coding Conventions): Recommend cl-lib over cl.
Date: Sun, 21 Oct 2012 19:18:58 -0700
User-agent: Bazaar (2.5.0)

------------------------------------------------------------
revno: 110614
committer: Glenn Morris <address@hidden>
branch nick: trunk
timestamp: Sun 2012-10-21 19:18:58 -0700
message:
  * doc/lispref/tips.texi (Coding Conventions): Recommend cl-lib over cl.
modified:
  doc/lispref/ChangeLog
  doc/lispref/tips.texi
=== modified file 'doc/lispref/ChangeLog'
--- a/doc/lispref/ChangeLog     2012-10-15 04:03:04 +0000
+++ b/doc/lispref/ChangeLog     2012-10-22 02:18:58 +0000
@@ -1,3 +1,7 @@
+2012-10-22  Glenn Morris  <address@hidden>
+
+       * tips.texi (Coding Conventions): Recommend cl-lib over cl.
+
 2012-10-15  Chong Yidong  <address@hidden>
 
        * macros.texi (Defining Macros): defmacro is now a macro.

=== modified file 'doc/lispref/tips.texi'
--- a/doc/lispref/tips.texi     2012-05-27 01:34:14 +0000
+++ b/doc/lispref/tips.texi     2012-10-22 02:18:58 +0000
@@ -120,15 +120,18 @@
 your file do not need to load the extra library.
 
 @item
-Please don't require the @code{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 @code{cl} at run time,
-that could cause name clashes for users who don't use that package.
+If you need Common Lisp extensions, use the @code{cl-lib} library
+rather than the old @code{cl} library.  The latter does not
+use a clean namespace (i.e., its definitions do not
+start with a @samp{cl-} prefix).  If your package loads @code{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 @code{cl} package at
-compile time, with @code{(eval-when-compile (require 'cl))}.  That's
+There is no problem with using the @code{cl} package at @emph{compile}
+time, with @code{(eval-when-compile (require 'cl))}.  That's
 sufficient for using the macros in the @code{cl} package, because the
-compiler expands them before generating the byte-code.
+compiler expands them before generating the byte-code.  It is still
+better to use the more modern @code{cl-lib} in this case, though.
 
 @item
 When defining a major mode, please follow the major mode


reply via email to

[Prev in Thread] Current Thread [Next in Thread]