changeset 71855:0fa817d8a084

(Coding Conventions): Explain why use cl at compile time.
author Richard M. Stallman <rms@gnu.org>
date Wed, 12 Jul 2006 16:07:17 +0000
parents a4944423be59
children 52fe532e1485
files lispref/tips.texi
diffstat 1 files changed, 3 insertions(+), 2 deletions(-) [+]
line wrap: on
line diff
--- a/lispref/tips.texi	Wed Jul 12 16:05:19 2006 +0000
+++ b/lispref/tips.texi	Wed Jul 12 16:07:17 2006 +0000
@@ -119,8 +119,9 @@
 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