From: Glenn Morris <rgm@gnu.org>
To: 25556@debbugs.gnu.org
Cc: Stefan Monnier <monnier@iro.umontreal.ca>,
David Engster <deng@randomsample.de>,
npostavs@users.sourceforge.net
Subject: bug#25556: 26.0.50.1; Requiring uncompiled eieio issues obsoletion warnings
Date: Thu, 15 Mar 2018 21:31:34 -0400 [thread overview]
Message-ID: <tlk1ucergp.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <87zii98srt.fsf@engster.org> (David Engster's message of "Sun, 29 Jan 2017 22:23:34 +0100")
David Engster wrote:
> Regarding eieio-object-name-string, the issue is indeed that it is first
> defined via cl-defgeneric with an obsolete declaration, which in turn
> means that any (uncompiled) cl-defmethod will issue an obsoletion
> warning (so in this case twice: for eieio and eieio-named in
> eieio-base.el).
>
> So couldn't we just simply remove the cl-defgeneric for
> eieio-object-name-string, and use make-obsolete instead?
>
> Stefan, what do you think?
Returning to this topic:
It seems eieio-object-name-string has been de-obsoleted, but the fact
that object-print is now obsolete causes 157 identical warnings
when bootstrapping:
eieio.el: `object-print' is an obsolete generic function (as of 26.1);
use `cl-print-object' instead.
Minimal example:
rm lisp/emacs-lisp/eieio.elc
and byte-compile any file that requires 'eieio.
It would be great if cl-defmethod only warned when it was in the file
actually being compiled.
next prev parent reply other threads:[~2018-03-16 1:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-27 20:38 bug#25556: 26.0.50.1; Requiring uncompiled eieio issues obsoletion warnings David Engster
2017-01-28 7:15 ` Eli Zaretskii
2017-01-28 8:39 ` David Engster
2017-01-28 14:31 ` npostavs
2017-01-28 21:15 ` David Engster
2017-01-29 16:20 ` npostavs
2017-01-29 21:23 ` David Engster
2018-03-16 1:31 ` Glenn Morris [this message]
2018-03-16 6:00 ` Glenn Morris
2018-03-16 12:14 ` Stefan Monnier
2018-03-17 0:42 ` Glenn Morris
2020-08-24 15:26 ` Lars Ingebrigtsen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=tlk1ucergp.fsf@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=25556@debbugs.gnu.org \
--cc=deng@randomsample.de \
--cc=monnier@iro.umontreal.ca \
--cc=npostavs@users.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.