[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#25556: 22.214.171.124; Requiring uncompiled eieio issues obsoletion warni
bug#25556: 126.96.36.199; Requiring uncompiled eieio issues obsoletion warnings
Sat, 28 Jan 2017 09:39:42 +0100
Gnus/5.13 (Gnus v5.13) Emacs/25.1 (gnu/linux)
Eli Zaretskii writes:
>> From: David Engster <address@hidden>
>> Date: Fri, 27 Jan 2017 21:38:58 +0100
>> I'm currently trying to fix compiler warnings during the CEDET compile
>> in Emacs master, but there's one annoying problem I'm unsure how to
>> fix. Whenever a file does (require 'eieio), and EIEIO is not yet
>> byte-compiled, those two warnings are issued:
>> ../../emacs-lisp/eieio.el: ‘eieio-object-name-string’ is an obsolete
>> generic function (as of 25.1); use ‘eieio-named’ instead.
>> ../../emacs-lisp/eieio.el: ‘destructor’ is an obsolete generic
>> function (as of 26.1).
>> Since EIEIO is compiled pretty late, one is flooded with these warnings
>> when compiling Emacs master. The warnings seems to come from the
>> cl-defgeneric for `eieio-object-name-string' and `destructor'. How can
>> this be dealt with?
> Is it possibel to arrange that these files be compiled sooner? We
> already have some targets for similar purposes in lisp/Makefile.
I'm sure that's possible, but why does the file that declares those
constructs obsolete *itself* throw these warnings? I was hoping that
this could be fixed instead.