GNU bug report logs -
#73881
31.0.50; Unexpected warnings about recursive occurrences of obsolete functions
Previous Next
Full log
View this message in rfc822 format
>> As for an easy fix, maybe something like this?
>>
>> diff --git a/lisp/emacs-lisp/bytecomp.el b/lisp/emacs-lisp/bytecomp.el
>> index 29e7882c851..edb8160a250 100644
>> --- a/lisp/emacs-lisp/bytecomp.el
>> +++ b/lisp/emacs-lisp/bytecomp.el
>> @@ -1533,6 +1533,7 @@ byte-compile-arglist-signature-string
>>
>> (defun byte-compile-function-warn (f nargs def)
>> (when (and (get f 'byte-obsolete-info)
>> + (not (eq f byte-compile-current-form)) ; Recursive call.
>> (not (memq f byte-compile-not-obsolete-funcs)))
>> (byte-compile-warn-obsolete f "function"))
>
> Thanks, let's see what others think about this.
Hmm... I distinctly remember writing code to try and silence
obsolescence warnings in the code coming from the same file as the
`make-obsolete` call.
If I installed that code into Emacs, clearly it's not doing its job.
..Hmm.. I think I see the problem: the code I wrote was for variables
rather than for functions:
;; 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.
(byte-defop-compiler-1 make-obsolete-variable)
(defun byte-compile-make-obsolete-variable (form)
(when (eq 'quote (car-safe (nth 1 form)))
(push (nth 1 (nth 1 form)) byte-compile-global-not-obsolete-vars))
(byte-compile-normal-call form))
So maybe we should just do the same for `make-obsolete`?
Stefan
This bug report was last modified 232 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.