unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Burton Samograd <burton@samograd.ca>
To: Glenn Morris <rgm@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: CL functions called at runtime
Date: Mon, 03 Dec 2012 13:00:27 -0700	[thread overview]
Message-ID: <kghhao2hpno.fsf@CDW764-BURTONS.QFTI.COM> (raw)
In-Reply-To: <0afw3m52ro.fsf@fencepost.gnu.org> (Glenn Morris's message of "Mon, 03 Dec 2012 14:55:39 -0500")

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



  reply	other threads:[~2012-12-03 20:00 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 [this message]
2012-12-03 20:22     ` Glenn Morris
2012-12-03 21:53       ` Stefan Monnier
2012-12-03 19:56 ` Pascal J. Bourguignon
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=kghhao2hpno.fsf@CDW764-BURTONS.QFTI.COM \
    --to=burton@samograd.ca \
    --cc=emacs-devel@gnu.org \
    --cc=rgm@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).