procyberian/emacs
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Add tests for some byte-compiler warnings

Browse source 
* test/lisp/emacs-lisp/bytecomp-tests.el
(bytecomp-warn/warn-interactive-only\.el)
(bytecomp-warn/warn-obsolete-defun\.el)
(bytecomp-warn/warn-obsolete-hook\.el)
(bytecomp-warn/warn-obsolete-variable-same-file\.el)
(bytecomp-warn/warn-obsolete-variable\.el): New tests.
* test/lisp/emacs-lisp/bytecomp-resources/warn-interactive-only.el:
* test/lisp/emacs-lisp/bytecomp-resources/warn-obsolete-defun.el:
* test/lisp/emacs-lisp/bytecomp-resources/warn-obsolete-hook.el:
* test/lisp/emacs-lisp/bytecomp-resources/warn-obsolete-variable-same-file.el:
* test/lisp/emacs-lisp/bytecomp-resources/warn-obsolete-variable.el:
New files.
This commit is contained in:
Stefan Kangas 2020-12-01 04:46:33 +01:00
parent 90a543e630
commit 4457b9590c
6 changed files with 49 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

13
test/lisp/emacs-lisp/bytecomp-resources/warn-obsolete-variable-same-file.el Normal file
View file

@ -0,0 +1,13 @@
;;; -*- lexical-binding: t -*-
(defvar foo-obsolete nil)
(make-obsolete-variable 'foo-obsolete nil "99.99")
;; From bytecomp.el:
;; If foo.el declares `toto' as obsolete, it is likely that foo.el will
;; actually use `toto' in order for this obsolete variable to still work
;; correctly, so paradoxically, while byte-compiling foo.el, the presence
;; of a make-obsolete-variable call for `toto' is an indication that `toto'
;; should not trigger obsolete-warnings in foo.el.
(defun foo ()
foo-obsolete)