GNU bug report logs - #39169
28.0.50; Confusing obsolete variable warnings in eieio-defclass-autoload

Previous Next

Full log

Message #20 received at 39169 <at> debbugs.gnu.org (full text, mbox):

From: Michael Heerdegen <michael_heerdegen <at> web.de>
To: Lars Ingebrigtsen <larsi <at> gnus.org>
Cc: 39169 <at> debbugs.gnu.org, Stefan Monnier <monnier <at> iro.umontreal.ca>
Subject: Re: bug#39169: 28.0.50; Confusing obsolete variable warnings in
 eieio-defclass-autoload
Date: Wed, 26 Aug 2020 17:30:56 +0200

Lars Ingebrigtsen <larsi <at> gnus.org> writes:

> But now I'm wondering why Michael isn't just setting/binding
> eieio-backward-compatibility to nil?  Then the warnings would go away,
> and he probably aren't using the compat symbols, anyway?

AFAIR, the situation is: I can do that file locally in my library, yes.

But any user of the library will still see those warnings.  It's likely
that this user uses the name "buffer-note" for a buffer-note, and the
warning text is meaningless for anybody who doesn't know what's going
on.

Michael.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.