diff options
| author | Alan Mackenzie <acm@muc.de> | 2007-07-24 08:18:12 +0000 |
|---|---|---|
| committer | Alan Mackenzie <acm@muc.de> | 2007-07-24 08:18:12 +0000 |
| commit | 2cb63a7c2354eb853c1aa58a25ac6d2392b87887 (patch) | |
| tree | 7928118063320207336d6afa678fd04df2d53b01 /lisp/emacs-lisp | |
| parent | 31386eea27a586c8ea8a79a5544f36718232c9a2 (diff) | |
| download | emacs-2cb63a7c2354eb853c1aa58a25ac6d2392b87887.tar.gz emacs-2cb63a7c2354eb853c1aa58a25ac6d2392b87887.tar.bz2 emacs-2cb63a7c2354eb853c1aa58a25ac6d2392b87887.zip | |
(byte-compile-from-buffer): initialise byte-compile-unresolved-functions
before rather than after a compilation.
(byte-compile-unresolved-functions): Amplify doc string.
Diffstat (limited to 'lisp/emacs-lisp')
| -rw-r--r-- | lisp/emacs-lisp/bytecomp.el | 14 |
1 files changed, 8 insertions, 6 deletions
diff --git a/lisp/emacs-lisp/bytecomp.el b/lisp/emacs-lisp/bytecomp.el index 8760f36775b..cdc93cf83d7 100644 --- a/lisp/emacs-lisp/bytecomp.el +++ b/lisp/emacs-lisp/bytecomp.el @@ -480,7 +480,8 @@ and we don't know the definition.") (defvar byte-compile-unresolved-functions nil "Alist of undefined functions to which calls have been compiled. -Used for warnings when the function is not known to be defined or is later +This variable is only significant whilst compiling an entire buffer. +Used for warnings when a function is not known to be defined or is later defined with incorrect args.") (defvar byte-compile-noruntime-functions nil @@ -1849,6 +1850,11 @@ With argument, insert value in current buffer after the form." (and filename (byte-compile-insert-header filename inbuffer outbuffer)) (with-current-buffer inbuffer (goto-char (point-min)) + ;; Should we always do this? When calling multiple files, it + ;; would be useful to delay this warning until all have been + ;; compiled. A: Yes! b-c-u-f might contain dross from a + ;; previous byte-compile. + (setq byte-compile-unresolved-functions nil) ;; Compile the forms from the input buffer. (while (progn @@ -1865,11 +1871,7 @@ With argument, insert value in current buffer after the form." ;; Make warnings about unresolved functions ;; give the end of the file as their position. (setq byte-compile-last-position (point-max)) - (byte-compile-warn-about-unresolved-functions) - ;; Should we always do this? When calling multiple files, it - ;; would be useful to delay this warning until all have - ;; been compiled. - (setq byte-compile-unresolved-functions nil)) + (byte-compile-warn-about-unresolved-functions)) ;; Fix up the header at the front of the output ;; if the buffer contains multibyte characters. (and filename (byte-compile-fix-header filename inbuffer outbuffer)))) |