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

diff --git a/lispref/tips.texi b/lispref/tips.texi
index c8cd4770113d4f7cfe4ff39c3c6a02d8450063d7..4dc24196272cf0d2f823be79376852ae327f0a89 100644 (file)
--- 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