From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Matt Swift Newsgroups: gmane.emacs.bugs Subject: (setq byte-compile-warnings '(unresolved)) does not work Date: Tue, 04 Mar 2003 04:00:20 -0500 Sender: bug-gnu-emacs-bounces+gnu-bug-gnu-emacs=m.gmane.org@gnu.org Message-ID: NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: main.gmane.org 1046770633 25776 80.91.224.249 (4 Mar 2003 09:37:13 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Tue, 4 Mar 2003 09:37:13 +0000 (UTC) Original-X-From: bug-gnu-emacs-bounces+gnu-bug-gnu-emacs=m.gmane.org@gnu.org Tue Mar 04 10:37:11 2003 Return-path: Original-Received: from monty-python.gnu.org ([199.232.76.173]) by main.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 18q8rH-0006hX-00 for ; Tue, 04 Mar 2003 10:37:11 +0100 Original-Received: from localhost ([127.0.0.1] helo=monty-python.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.10.13) id 18q8rG-00024i-02 for gnu-bug-gnu-emacs@m.gmane.org; Tue, 04 Mar 2003 04:37:10 -0500 Original-Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13) id 18q8qf-0001VX-00 for bug-gnu-emacs@gnu.org; Tue, 04 Mar 2003 04:36:33 -0500 Original-Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13) id 18q8qD-0000yf-00 for bug-gnu-emacs@gnu.org; Tue, 04 Mar 2003 04:36:05 -0500 Original-Received: from pool-68-160-53-216.bos.east.verizon.net ([68.160.53.216] helo=beth.swift.xxx) by monty-python.gnu.org with esmtp (Exim 4.10.13) id 18q8pT-0000aq-00 for bug-gnu-emacs@gnu.org; Tue, 04 Mar 2003 04:35:20 -0500 Original-Received: from beth.swift.xxx (swift@localhost.swift.xxx [127.0.0.1]) h2490NH8018096verify=FAIL) for ; Tue, 4 Mar 2003 04:00:23 -0500 Original-Received: (from swift@localhost) by beth.swift.xxx (8.12.7/8.12.7/Debian-2) id h2490KnV018094; Tue, 4 Mar 2003 04:00:20 -0500 Original-To: bug-gnu-emacs@gnu.org User-Agent: Gnus/5.090016 (Oort Gnus v0.16) Emacs/21.2 (i386-debian-linux-gnu) X-Mailscanner: clean (beth.swift.xxx) X-BeenThere: bug-gnu-emacs@gnu.org X-Mailman-Version: 2.1b5 Precedence: list List-Id: Bug reports for GNU Emacs, the Swiss army knife of text editors List-Help: List-Post: List-Subscribe: , List-Archive: List-Unsubscribe: , Errors-To: bug-gnu-emacs-bounces+gnu-bug-gnu-emacs=m.gmane.org@gnu.org Xref: main.gmane.org gmane.emacs.bugs:4551 X-Report-Spam: http://spam.gmane.org/gmane.emacs.bugs:4551 Setting `byte-compile-warnings' to '(unresolved) results in no compiler warnings about unresolved functions in 21.2 and this week's CVS Emacs 21.3. The reason is that the list `byte-compile-unresolved-functions' is maintained properly only when the 'callargs and 'redefine warnings are also selected. The list is augmented only in `byte-compile-callargs-warn', which is called only if the 'callargs warning is selected. The list is trimmed only in `byte-compile-defalias-warn' and `byte-compile-if', which are called only when compiling invocations of `defalias' and `if', and `byte-compile-arglist-warn', which is called only if the 'redefine warning is selected. To demonstrate, save the following in its own file and \C-x\C-e (`eval-last-sexp') with point at the end. Uncomment `callargs' and repeat. ;;;;;;;;;;;;;;;;;;;;;; (or (and (fboundp 'zzzz) (progn (zzzz) (error "whoops"))) (and (setq byte-compile-warnings '( unresolved ;; callargs )) (byte-compile-file (buffer-file-name))))