unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: rms@gnu.org
Cc: dann@ics.uci.edu, emacs-devel@gnu.org
Subject: Re: byte compiler warnings when bootstrapping
Date: Tue, 23 Oct 2007 10:21:30 -0400	[thread overview]
Message-ID: <jwv4pgiylkk.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <E1IkDw2-0007aO-Vq@fencepost.gnu.org> (Richard Stallman's message of "Tue\, 23 Oct 2007 03\:12\:18 -0400")

>       (require-lazily <feature>)

>     which would behave similarly to `require' except that the byte-compiler
>     would replace it with a bunch of autoloads.  so the package would only be
>     "required" when one of its functions was used.

> I have a bad feeling about that -- that it would produce scads of autoloads
> which are not needed.  Also, I don't think it is needed in any of the existing
> cases of warnings we would like to suppress.

The intention is for the byte-compiler to take the intersection of the
functions defined by <feature> and the functions used in the file being
byte-compiled.

So I expect that in general it will not lead to tons of autoloads that are
not needed.  Of course, some of the autoloads will not be needed because
some of those functions will only ever be called after calling another one
of those autoloaded functions (like the example of calling
info-read-node-name after calling `info').  And actually, the byte-compiler
could even optimize away some of those cases.


        Stefan

  reply	other threads:[~2007-10-23 14:21 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-21  7:38 byte compiler warnings when bootstrapping Dan Nicolaescu
2007-10-21  9:50 ` martin rudalics
2007-10-22  9:00   ` Richard Stallman
2007-10-22 20:25     ` Eli Zaretskii
2007-10-23 10:39       ` Richard Stallman
2007-10-21 14:05 ` Stefan Monnier
2007-10-21 15:58   ` Dan Nicolaescu
2007-10-21 16:15     ` David Kastrup
2007-10-21 16:33       ` Dan Nicolaescu
2007-10-21 18:44         ` David Kastrup
2007-10-21 19:38     ` Stefan Monnier
2007-10-21 23:24       ` Bob Rogers
2007-10-23  7:12         ` Richard Stallman
2007-10-23  7:12       ` Richard Stallman
2007-10-23 14:21         ` Stefan Monnier [this message]
2007-10-24  2:49           ` Richard Stallman
2007-10-24  3:49             ` Stefan Monnier
2007-10-25  2:10               ` Richard Stallman
2007-10-23 14:23         ` Stefan Monnier

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=jwv4pgiylkk.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=dann@ics.uci.edu \
    --cc=emacs-devel@gnu.org \
    --cc=rms@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).