unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: David Engster <deng@randomsample.de>
Cc: 25556@debbugs.gnu.org
Subject: bug#25556: 26.0.50.1; Requiring uncompiled eieio issues obsoletion warnings
Date: Mon, 24 Aug 2020 17:26:11 +0200	[thread overview]
Message-ID: <87ft8c83qk.fsf@gnus.org> (raw)
In-Reply-To: <878tpw1bml.fsf@engster.org> (David Engster's message of "Fri, 27 Jan 2017 21:38:58 +0100")

David Engster <deng@randomsample.de> writes:

> 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?

I think all of this was fixed last year, when all the obsolete eieio
function calls were rewritten, so I'm closing this bug report.  If
there's still any issues here, please respond to the debbugs address and
we'll reopen the report.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





      parent reply	other threads:[~2020-08-24 15:26 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
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 [this message]

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87ft8c83qk.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=25556@debbugs.gnu.org \
    --cc=deng@randomsample.de \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).