From: Richard M. Stallman <rms@gnu.org>
Date: Wed, 12 Jul 2006 16:07:17 +0000 (+0000)
Subject: (Coding Conventions): Explain why use cl at compile time.
X-Git-Tag: emacs-pretest-22.0.90~1483
X-Git-Url: http://git.eshelyaron.com/gitweb/?a=commitdiff_plain;h=9aa9b967b95678f96cdbbeeae61c8b29bf7fc589;p=emacs.git

(Coding Conventions): Explain why use cl at compile time.
---

diff --git a/lispref/tips.texi b/lispref/tips.texi
index c8cd4770113..4dc24196272 100644
--- a/lispref/tips.texi
+++ b/lispref/tips.texi
@@ -119,8 +119,9 @@ 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.
 
 However, there is no problem with using the @code{cl} package at
-compile time, e.g. for macros, with
-@code{(eval-when-compile (require 'cl))}.
+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.
 
 @item
 When defining a major mode, please follow the major mode