From: "Stefan Monnier" <monnier+gnu/emacs@rum.cs.yale.edu>
Cc: d.love@dl.ac.uk, emacs-devel@gnu.org
Subject: Re: bytecomp warning for CL functions
Date: Wed, 26 Jun 2002 10:10:28 -0400 [thread overview]
Message-ID: <200206261410.g5QEASU11961@rum.cs.yale.edu> (raw)
In-Reply-To: E17MznG-0008Pl-00@fencepost.gnu.org
> That is a good idea--Eli, would you please install it?
>
> I think it would be even better if these warnings were issued by default
> whenever the file does not include cl. Does anyone see a reason not
> to do that?
Could someone explain to me what this really does ?
I had installed a hack that tries to notice when you call a function
that will not be available at runtime (because the library
was loaded via (eval-when-compile (require 'LIB)) as is done for CL).
It had a bug that I just fixed so it should be a bit more useful now.
In what way does Dave's code differ ?
I notice for example that it warns about code that uses `values' but
since the CVS has replaced the defvalias with a defsubst for `values',
a call to `values' gets replaced during byte-compilation so that
it works just fine even without using CL at runtime.
Admittedly, my hack is just that: a hack. And it's not reliable.
But it is more genric and covers more cases. So my question is:
which cases does Dave's code cover that mine doesn't.
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.
Stefan
next prev parent reply other threads:[~2002-06-26 14:10 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 [this message]
2002-07-01 18:11 ` Dave Love
2002-07-02 19:45 ` Richard Stallman
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=200206261410.g5QEASU11961@rum.cs.yale.edu \
--to=monnier+gnu/emacs@rum.cs.yale.edu \
--cc=d.love@dl.ac.uk \
--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).