[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: (setq byte-compile-warnings '(unresolved)) does not work

From: Richard Stallman
Subject: Re: (setq byte-compile-warnings '(unresolved)) does not work
Date: Wed, 05 Mar 2003 15:46:46 -0500

      The reason is that the list
    `byte-compile-unresolved-functions' is maintained properly only when
    the `callargs' and `redefine' warnings are also selected.

I think the way to fix this is to move the code that maintains the
list outside the subroutines `byte-compile-callargs-warn' and
`byte-compile-arglist-warn', so that it will update the list even
if those functions are not called.

Would someone like to write the code?

Here's the test case:

    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


     (and (fboundp 'zzzz) (progn (zzzz) (error "whoops")))
      (setq byte-compile-warnings '(
                                    ;; callargs
      (byte-compile-file (buffer-file-name))))

reply via email to

[Prev in Thread] Current Thread [Next in Thread]