>
>> Also, while intersection below is a function defined in cl-seq, the use
>> of `intersection' in ob.el refers to a local function and not the cl-seq
>> function, so it should be fine.
>
> The byte-compiler thinks otherwise, so I'd check that assumption
> again... but it might be a good idea to
Eric Schulte writes:
> Is there a convention for which macros from cl-macs are allowable and
> which are forbidden?
You might want to ask on the Emacs list, but my understanding is that no
Emacs core packages should depend on cl _at runtime_, but it is OK to
use the cl package during byte-compila
Thanks for catching this, I've just pushed up a fix.
Is there a convention for which macros from cl-macs are allowable and
which are forbidden? For example `flet' is used extensively throughout
the Org-mode code base. Is the convention that macros are allowable
while functions are not?
Also, wh
The sources in ob.el have picked up several runtime invocations to
functions from the cl package via two commits from Eric:
fc92b2e2 lisp/ob.el (let ((tempvar (gensym "file")))
fc92b2e2 lisp/ob.el (let ((tempvar (gensym "file")))
fc92b2e2 lisp/ob.el (let ((tempvar (gensym "file")))
fc92b2e2 lisp/
