unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
Cc: monnier+gnu/emacs@rum.cs.yale.edu, emacs-devel@gnu.org
Subject: Re: bytecomp warning for CL functions
Date: Tue, 2 Jul 2002 13:45:59 -0600 (MDT)	[thread overview]
Message-ID: <200207021945.g62Jjxa02009@aztec.santafe.edu> (raw)
In-Reply-To: <rzqofdrfhdk.fsf@albion.dl.ac.uk> (message from Dave Love on 01 Jul 2002 19:11:19 +0100)

    > What I'm trying to figue out is if there is a way to get the benefits
    > of Dave's code without having to hard-code any particular list
    > of functions.

That ought to be a small and simple generalization, if we ever want to
make it.  I don't see a need to make it now.  I will install this
code, together with some changes so that these warnings are enabled
automatically whenever the file being compiled does not do (require
'cl) at run time.

  reply	other threads:[~2002-07-02 19:45 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <rzqhejse35l.fsf@albion.dl.ac.uk>
2002-06-25 23:32 ` bytecomp warning for CL functions Richard Stallman
2002-06-26 14:10   ` Stefan Monnier
2002-07-01 18:11     ` Dave Love
2002-07-02 19:45       ` Richard Stallman [this message]
2002-07-03  7:21         ` Juanma Barranquero
2002-07-08 18:20           ` Richard Stallman
2002-07-18 18:48           ` Dave Love
2002-07-19  6:09             ` Juanma Barranquero
2002-07-19 16:54             ` Richard Stallman
2002-07-08 18:19     ` Richard Stallman
2002-07-18 18:53       ` Dave Love
2002-07-19 16:54         ` Richard Stallman
2002-07-19 17:49           ` Stefan Monnier
2002-07-20  0:35             ` Richard Stallman
2002-07-29 22:46           ` Dave Love
2002-07-30 18:46             ` Richard Stallman
2002-07-08 18:20     ` Richard Stallman
2002-07-08 19:30       ` Luc Teirlinck
2002-07-09 18:51         ` Richard Stallman
2002-07-18 18:34         ` Dave Love
2002-07-19 16:54           ` Richard Stallman
2002-07-22 22:15             ` Dave Love

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=200207021945.g62Jjxa02009@aztec.santafe.edu \
    --to=rms@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=monnier+gnu/emacs@rum.cs.yale.edu \
    /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).