aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorRichard M. Stallman2006-07-12 16:07:17 +0000
committerRichard M. Stallman2006-07-12 16:07:17 +0000
commit9aa9b967b95678f96cdbbeeae61c8b29bf7fc589 (patch)
tree3c0f9ace973142df17c887173c3676c11a50ed8e
parentf911a4454addf2b3d39f52c6e7ac83d5d1c27032 (diff)
downloademacs-9aa9b967b95678f96cdbbeeae61c8b29bf7fc589.tar.gz
emacs-9aa9b967b95678f96cdbbeeae61c8b29bf7fc589.zip
(Coding Conventions): Explain why use cl at compile time.
-rw-r--r--lispref/tips.texi5
1 files changed, 3 insertions, 2 deletions
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,
119that could cause name clashes for users who don't use that package. 119that could cause name clashes for users who don't use that package.
120 120
121However, there is no problem with using the @code{cl} package at 121However, there is no problem with using the @code{cl} package at
122compile time, e.g. for macros, with 122compile time, with @code{(eval-when-compile (require 'cl))}. That's
123@code{(eval-when-compile (require 'cl))}. 123sufficient for using the macros in the @code{cl} package, because the
124compiler expands them before generating the byte-code.
124 125
125@item 126@item
126When defining a major mode, please follow the major mode 127When defining a major mode, please follow the major mode