Re: (require 'cl) problem

[Pascal Bourguignon]

"It's me FKtPp ;)" <m_pupil@163.com> writes:

> The Emacs Lisp Programing Standard said:
> ,----
> | 
> |    * Please don't require the `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 `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 `cl' package at compile
> |      time, for the sake of macros.  You do that like this:
> | 
> |           (eval-when-compile (require 'cl))
> `----

This should only apply to emacs sources themselves!  Not to your user
code.  You are free to use common-lisp.
 
> But when i test this piece of code (byte-compile and restart emacs and
> load the elc)
> 
> ,----[ test.el ]
> | ;; just want to test cl
> | 
> | ;;; Code:
> | 
> | (eval-when-compile (require 'cl))
> | 
> | (defun fktpp-test-case ()
> |   "test cl library"
> |   (interactive)
> |   (message (if (oddp 22)
> |            "yes it's odd"
> |          "no it isn't")))
> | 
> | (provide 'test)
> | ;;; test.el ends here
> `----
> 
> it always tell me the symbol oddp didn't defined. why ? Is there any
> thing illegal in my code?

Nothing illegal, but use (require 'cl) instead of (eval-when-compile
(require 'cl)), or even better, forget emacs and use true Common-Lisp
and the Hemlock editor! ;-)

-- 
__Pascal Bourguignon__                     http://www.informatimago.com/

Our enemies are innovative and resourceful, and so are we. They never
stop thinking about new ways to harm our country and our people, and
neither do we.