Re: Post-22.1 development?

[Andreas Schwab]

Michael Albinus <address@hidden> writes:

> address@hidden (Johan Bockgård) writes:
>
>> The change was unnecessarily drastic.
>>
>>      However, there is no problem with using the `cl' package at
>>      compile time, with `(eval-when-compile (require 'cl))'.  That's
>>      sufficient for using the macros in the `cl' package, because the
>>      compiler expands them before generating the byte-code.
>>
>>      -- (info "(elisp)Coding Conventions")
>
> But this would mean that one cannot use such a package if it is NOT
> byte compiled.

Why?  The require is still evaluated when interpreted.

eval-when-compile is a Lisp macro in `byte-run.el'.
(eval-when-compile &rest BODY)

Like `progn', but evaluates the body at compile time if you're compiling.
Thus, the result of the body appears to the compiler as a quoted constant.
In interpreted code, this is entirely equivalent to `progn'.

Andreas.

-- 
Andreas Schwab, SuSE Labs, address@hidden
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
PGP key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."