Re: byte-compile / cl package / warnings

Re: byte-compile / cl package / warnings

[David Reitter]

Johan BockgÃrd wrote:


> Read (info "(elisp)Coding Conventions")
>

Thanks very much for the hint.

It looks like either the warning is obsolete, or the 'cl' package  
goes against Emacs naming conventions. But I assume it would do so  
for a good reason (compatibility with common lisp).

For everyone interested, here's an excerpt from the above info page:

    * 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, with `(eval-when-compile (require 'cl))'.

Re: byte-compile / cl package / warnings

[Johan Bockgård]

Read (info "(elisp)Coding Conventions")

-- 
Johan Bockgård

Re: byte-compile / cl package / warnings

[Pascal Bourguignon]

David Reitter <david.reitter@gmail.com> writes:

> Hi,
> I often get warnings like
>
> "Function `set-difference' from cl package
>      called at runtime"
>
> when byte-compiling stuff.
>
> Isn't it safe to call stuff from the cl package from byte-compiled code?
> I looked into the byte-compile source, and I found that the cl
> package documentation says that it's safe to require 'cl.
>
> So why do I get this warning, and do I need to react?

Yes:
1- send an email to rms@gnu.org complaining about this.
2- edit the sources of emacs to remove this warning.
3- send in a patch.


When RMS will have recevied 10,000 identical patches from 10,000
different complaining users, perhaps he'll include it.

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

Nobody can fix the economy.  Nobody can be trusted with their finger
on the button.  Nobody's perfect.  VOTE FOR NOBODY.

byte-compile / cl package / warnings

[David Reitter]

Hi,
I often get warnings like

"Function `set-difference' from cl package
     called at runtime"

when byte-compiling stuff.

Isn't it safe to call stuff from the cl package from byte-compiled code?
I looked into the byte-compile source, and I found that the cl  
package documentation says that it's safe to require 'cl.

So why do I get this warning, and do I need to react?

Thanks
Dave