unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: zyd <zyd-p@proton.me>, 73505@debbugs.gnu.org
Subject: bug#73505: EIEIO manual out of date, doesn't reflect current functionality
Date: Fri, 27 Sep 2024 08:48:07 -0400	[thread overview]
Message-ID: <jwvh6a11d9l.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <86setl8tue.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 27 Sep 2024 09:59:53 +0300")

> But this isn't true at all, EIEIO has both of these features fully
> functional in fact.

It's both true and false:

- EIEIO "has" none of those things because the defmethod stuff is now
  provided by something else than EIEIO.  EIEIO only provides `defclass`
  and associated functions (e.g. `slot-value`).

- But yes, the text is out of date because you can now use these
  features (with EIEIO objects, with defstruct objects, with
  oclosure objects, ...).

> The EIEIO manual states that it provides method functionality for
> Emacs Lisp.  The manual has whole sections devoted to both
> cl-defmethod and cl-defgeneric and refers to them as part of its
> corpus.  It has documentation for both.
>
>     (info "(eieio) Generics")
>     (info "(eieio) Methods")

This structure is a left-over from when generics were provided by EIEIO.
We should clarify.

> And as far as I can tell there is no eieio-specific defmethod or
> defgeneric macros that aren't cl-defmethod and cl-defgeneric.
> So I really doubt that I'm in error here.

Actually, `eieio-compat` still provides the old `defmethod` and
`defgeneric` (without `cl-`)


        Stefan






  parent reply	other threads:[~2024-09-27 12:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-26 22:45 bug#73505: EIEIO manual out of date, doesn't reflect current functionality zyd via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-09-27  6:59 ` Eli Zaretskii
2024-09-27  8:08   ` zyd via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-09-27 12:48   ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2024-09-27 13:01     ` Eli Zaretskii
2024-09-27 13:15     ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-09-27 13:23       ` Eli Zaretskii
2024-09-27 14:35         ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors

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=jwvh6a11d9l.fsf-monnier+emacs@gnu.org \
    --to=bug-gnu-emacs@gnu.org \
    --cc=73505@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    --cc=zyd-p@proton.me \
    /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).