CL functions called at runtime

CL functions called at runtime

[Burton Samograd]

Hi,

I seemed to have missed the dicussion about the warnings being generated
by the byte compiler about CL functions being called at runtime.  Now
I'm seeing them in my code for useful functions like remove-if.

Could someone explain why these warnings are being generated?

--
Burton Samograd

Re: CL functions called at runtime

[Stefan Monnier]

> I seemed to have missed the dicussion about the warnings being generated
> by the byte compiler about CL functions being called at runtime.  Now
> I'm seeing them in my code for useful functions like remove-if.
> Could someone explain why these warnings are being generated?

There are different such warnings for different cases, so please specify
precisely what you see,


        Stefan

Re: CL functions called at runtime

[Burton Samograd]

Stefan Monnier <monnier@IRO.UMontreal.CA> writes:

>> I seemed to have missed the dicussion about the warnings being generated
>> by the byte compiler about CL functions being called at runtime.  Now
>> I'm seeing them in my code for useful functions like remove-if.
>> Could someone explain why these warnings are being generated?
>
> There are different such warnings for different cases, so please specify
> precisely what you see,

I'm seeing messages like "CL function 'remove-if' called at runtime."
Someone else suggested using cl-lib but I assume that's an external
package that I should install, correct?  

I have mostly been writing in Common Lisp prior to starting a new
project in Emacs Lisp only so I find certain CL functions useful and
wouldn't mind getting rid of the warnings when I compile the code.  If
downloading and install cl-lib and using the cl- prefix function will do
the trick then I'm ok with that.

--
Burton Samograd

Re: CL functions called at runtime

[Glenn Morris]

Burton Samograd wrote:

> I seemed to have missed the dicussion about the warnings being generated
> by the byte compiler about CL functions being called at runtime.

Probably because it happened decades ago.

>  Now I'm seeing them in my code for useful functions like remove-if.

They've always been there.

> Could someone explain why these warnings are being generated?

No point repeating ancient history. Search the archives, read the elisp
manual "tips" section; or use cl-lib instead.

Re: CL functions called at runtime

[Burton Samograd]

Glenn Morris <rgm@gnu.org> writes:

> Burton Samograd wrote:
>
>> I seemed to have missed the dicussion about the warnings being generated
>> by the byte compiler about CL functions being called at runtime.
>
> Probably because it happened decades ago.

Ok, I thought these warnings were added more recently.  Maybe I was
thinking of the cl-lib discussion that's been going on.

>
>>  Now I'm seeing them in my code for useful functions like remove-if.
>
> They've always been there.

Now I'm seeing them because I am actaully writing more elisp code rather
than little snippets.  I've just been noticing that the build is
complaining a lot more about various deprecated functions/macros like
flet (use cl-flet) more now so I thought all of the warnings were of a
newer character.

>
>> Could someone explain why these warnings are being generated?
>
> No point repeating ancient history. Search the archives, read the elisp
> manual "tips" section; or use cl-lib instead.

cl-lib is an external package, correct?

--
Burton Samograd

Re: CL functions called at runtime

[Glenn Morris]

Burton Samograd wrote:

> cl-lib is an external package, correct?

No. Included in 24.3+.

Re: CL functions called at runtime

[Stefan Monnier]

>> cl-lib is an external package, correct?
> No. Included in 24.3+.

It's also an external package available via ELPA for Emacs<24.3.


        Stefan

Re: CL functions called at runtime

[Pascal J. Bourguignon]

Burton Samograd <burton@samograd.ca> writes:

> Hi,
>
> I seemed to have missed the dicussion about the warnings being generated
> by the byte compiler about CL functions being called at runtime.  Now
> I'm seeing them in my code for useful functions like remove-if.
>
> Could someone explain why these warnings are being generated?

That's because the functions defined in the file cl.el (and associated
files) are not deemed "pure" emacs lisp enough.  (Is the actual reason
because RMS doesn't like Common Lisp, or because they represent a layer
above emacs lisp and therefore may be slower than native emacs lisp
functions?  Some other reason I don't know?)  It is accepted that they
are used at macro expansion time, in emacs code distributed by the FSF,
but the FSF doesn't want to distribute emacs code that depend on them at
run-time.


Notice however that if you don't have the intention to have your code
integrated with the GNU emacs distribution, then this warning is totally
irrelevant: you can make your code dependant on cl.el as you can make it
dependent on any other emacs package, coming from the FSF or from any
third party.


I have this in my ~/.emacs to disable those warnings:

(require 'bytecomp)
(byte-compile-disable-warning 'cl-functions)


-- 
__Pascal Bourguignon__                     http://www.informatimago.com/
A bad day in () is better than a good day in {}.

Re: CL functions called at runtime

[Daniel Colascione]

[-- Attachment #1: Type: text/plain, Size: 449 bytes --]

On 12/3/12 10:55 AM, Burton Samograd wrote:
> Hi,
> 
> I seemed to have missed the dicussion about the warnings being generated
> by the byte compiler about CL functions being called at runtime.  Now
> I'm seeing them in my code for useful functions like remove-if.

(defadvice byte-compile-warn (around shut-up-about-cl activate compile)
  (let* ((fmt (ad-get-arg 0)))
    (unless (string-match "cl package" fmt)
      ad-do-it)))




[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 235 bytes --]

Re: CL functions called at runtime

[Burton Samograd]

Daniel Colascione <dancol@dancol.org> writes:

> On 12/3/12 10:55 AM, Burton Samograd wrote:
>> Hi,
>> 
>> I seemed to have missed the dicussion about the warnings being generated
>> by the byte compiler about CL functions being called at runtime.  Now
>> I'm seeing them in my code for useful functions like remove-if.
>
> (defadvice byte-compile-warn (around shut-up-about-cl activate compile)
>   (let* ((fmt (ad-get-arg 0)))
>     (unless (string-match "cl package" fmt)
>       ad-do-it)))

Excellent, thank you.

--
Burton Samograd

Re: CL functions called at runtime

[Grégoire Jadi]

Burton Samograd <burton@samograd.ca> writes:

> Daniel Colascione <dancol@dancol.org> writes:
>
>> On 12/3/12 10:55 AM, Burton Samograd wrote:
>>> Hi,
>>> 
>>> I seemed to have missed the dicussion about the warnings being generated
>>> by the byte compiler about CL functions being called at runtime.  Now
>>> I'm seeing them in my code for useful functions like remove-if.
>>
>> (defadvice byte-compile-warn (around shut-up-about-cl activate compile)
>>   (let* ((fmt (ad-get-arg 0)))
>>     (unless (string-match "cl package" fmt)
>>       ad-do-it)))
>
> Excellent, thank you.

Or (byte-compile-disable-warning 'cl-functions)

Re: CL functions called at runtime

[Glenn Morris]

Daniel Colascione wrote:

> (defadvice byte-compile-warn (around shut-up-about-cl activate compile)
>   (let* ((fmt (ad-get-arg 0)))
>     (unless (string-match "cl package" fmt)
>       ad-do-it)))

(setq byte-compile-warnings '(not cl-functions))

Also works as a file-local.