unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Pascal J. Bourguignon" <pjb@informatimago.com>
To: emacs-devel@gnu.org
Subject: Re: CL functions called at runtime
Date: Mon, 03 Dec 2012 20:56:34 +0100	[thread overview]
Message-ID: <87mwxuvril.fsf@kuiper.lan.informatimago.com> (raw)
In-Reply-To: kghpq2rge3w.fsf@CDW764-BURTONS.QFTI.COM

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 {}.




  parent reply	other threads:[~2012-12-03 19:56 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-03 18:55 CL functions called at runtime Burton Samograd
2012-12-03 19:54 ` Stefan Monnier
2012-12-03 20:03   ` Burton Samograd
2012-12-03 19:55 ` Glenn Morris
2012-12-03 20:00   ` Burton Samograd
2012-12-03 20:22     ` Glenn Morris
2012-12-03 21:53       ` Stefan Monnier
2012-12-03 19:56 ` Pascal J. Bourguignon [this message]
2012-12-03 19:59 ` Daniel Colascione
2012-12-03 20:05   ` Burton Samograd
2012-12-03 23:05     ` Grégoire Jadi
2012-12-03 20:21   ` Glenn Morris

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87mwxuvril.fsf@kuiper.lan.informatimago.com \
    --to=pjb@informatimago.com \
    --cc=emacs-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).