From: zyd via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>,
"monnier@iro.umontreal.ca" <monnier@iro.umontreal.ca>,
"73505@debbugs.gnu.org" <73505@debbugs.gnu.org>
Subject: bug#73505: EIEIO manual out of date, doesn't reflect current functionality
Date: Fri, 27 Sep 2024 08:08:28 +0000 [thread overview]
Message-ID: <Ta6-8MrmLxaNAplhEwPkAvDg15miPTf4oEn4Y-bTRVsGb4kEVORWinQ3LvMV6WFG-_XskFHcr9L3BkT9uf4Wn3nFkQaIfzfhzHbanXEPhAs=@proton.me> (raw)
In-Reply-To: <86setl8tue.fsf@gnu.org>
On Friday, September 27th, 2024 at 12:59 AM, Eli Zaretskii <eliz@gnu.org> wrote:
> You are using above cl-defgeneric and cl-defmethod, which are not part of
> EIEIO. So I think the EIEIO manual is not mistaken in what it says. But maybe
> I'm missing something. Adding Stefan who might have comments.
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")
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.
next prev parent reply other threads:[~2024-09-27 8:08 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 [this message]
2024-09-27 12:48 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
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='Ta6-8MrmLxaNAplhEwPkAvDg15miPTf4oEn4Y-bTRVsGb4kEVORWinQ3LvMV6WFG-_XskFHcr9L3BkT9uf4Wn3nFkQaIfzfhzHbanXEPhAs=@proton.me' \
--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).