From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: byte compiler warnings when bootstrapping Date: Tue, 23 Oct 2007 10:21:30 -0400 Message-ID: References: <200710210738.l9L7cIGs012673@oogie-boogie.ics.uci.edu> <200710211558.l9LFwIBv003882@oogie-boogie.ics.uci.edu> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1193149337 8009 80.91.229.12 (23 Oct 2007 14:22:17 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 23 Oct 2007 14:22:17 +0000 (UTC) Cc: dann@ics.uci.edu, emacs-devel@gnu.org To: rms@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Oct 23 16:22:14 2007 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1IkKdn-0007Pq-O1 for ged-emacs-devel@m.gmane.org; Tue, 23 Oct 2007 16:21:56 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1IkKdf-0008WO-NE for ged-emacs-devel@m.gmane.org; Tue, 23 Oct 2007 10:21:47 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1IkKdc-0008W9-Pr for emacs-devel@gnu.org; Tue, 23 Oct 2007 10:21:44 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1IkKdY-0008Vc-Tm for emacs-devel@gnu.org; Tue, 23 Oct 2007 10:21:44 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1IkKdY-0008VZ-NT for emacs-devel@gnu.org; Tue, 23 Oct 2007 10:21:40 -0400 Original-Received: from tomts36.bellnexxia.net ([209.226.175.93] helo=tomts36-srv.bellnexxia.net) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1IkKdQ-0006wQ-Ra; Tue, 23 Oct 2007 10:21:33 -0400 Original-Received: from pastel.home ([74.12.205.156]) by tomts36-srv.bellnexxia.net (InterMail vM.5.01.06.13 201-253-122-130-113-20050324) with ESMTP id <20071023142130.RSPW7990.tomts36-srv.bellnexxia.net@pastel.home>; Tue, 23 Oct 2007 10:21:30 -0400 Original-Received: by pastel.home (Postfix, from userid 20848) id 582488564; Tue, 23 Oct 2007 10:21:29 -0400 (EDT) In-Reply-To: (Richard Stallman's message of "Tue\, 23 Oct 2007 03\:12\:18 -0400") User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/23.0.50 (gnu/linux) X-detected-kernel: by monty-python.gnu.org: Solaris 8 (1) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:81562 Archived-At: > (require-lazily ) > 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 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