diff --git a/lisp/ChangeLog b/lisp/ChangeLog index cd33d38a498..593a390b91a 100644 --- a/lisp/ChangeLog +++ b/lisp/ChangeLog @@ -1,5 +1,8 @@ 2007-08-22 Stefan Monnier + * emacs-lisp/bytecomp.el (byte-compile-from-buffer): Display a big fat + warning if the file uses old style backquotes. + * emacs-lisp/bytecomp.el (byte-compile-log-file) (byte-recompile-directory, byte-compile-file) (byte-compile-from-buffer): Use with-current-buffer. diff --git a/lisp/emacs-lisp/bytecomp.el b/lisp/emacs-lisp/bytecomp.el index 12fab768db5..5a7f96fb988 100644 --- a/lisp/emacs-lisp/bytecomp.el +++ b/lisp/emacs-lisp/bytecomp.el @@ -1821,6 +1821,7 @@ With argument, insert value in current buffer after the form." ;; new in Emacs 22.1. (read-with-symbol-positions inbuffer) (read-symbol-positions-list nil) + (old-style-backquotes nil) ;; #### This is bound in b-c-close-variables. ;; (byte-compile-warnings (if (eq byte-compile-warnings t) ;; byte-compile-warning-types @@ -1865,7 +1866,12 @@ 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)) + (byte-compile-warn-about-unresolved-functions) + ;; Warn about the use of old-style backquotes. + (when old-style-backquotes + (byte-compile-warn "!! The file uses old-style backquotes !! +This functionality has been obsolete for more than 10 years already +and will be removed soon. See (elisp)Backquote in the manual."))) ;; 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)))) diff --git a/lispref/macros.texi b/lispref/macros.texi index 6dea53ac983..b62c8b99d74 100644 --- a/lispref/macros.texi +++ b/lispref/macros.texi @@ -365,7 +365,7 @@ whitespace between the @samp{`}, @samp{,} or @samp{,@@} and the following expression. This syntax is still accepted, for compatibility with old Emacs -versions, but we recommend not using it in new programs. +versions, but support for it will soon disappear. @node Problems with Macros @section Common Problems Using Macros