From: Zhu Zihao <all_but_last@163.com>
To: Jonas Bernoulli <jonas@bernoul.li>
Cc: emacs-devel@gnu.org, Stefan Monnier <monnier@iro.umontreal.ca>,
Zhu Zihao <all_but_last@163.com>
Subject: Re: Slot accessing issues in EIEIO
Date: Thu, 07 May 2020 22:52:00 +0800 [thread overview]
Message-ID: <87zhajg5m7.wl-all_but_last@163.com> (raw)
In-Reply-To: <87k11nzvc2.fsf@bernoul.li>
On Thu, 07 May 2020 22:13:49 +0800,
Jonas Bernoulli wrote:
> That sounds too complicated for my use-cases at least, and I don't see
> what we gain by doing that except not having to advice `eieio-oref' and
> `eieio-oset', which by the way I don't think is all that horrible.
Yes, any hack based on slot-missing or slot-unbound looks like a kind of
anti-pattern.
I've mentioned slot-value-using-class above, but this was based on the
MOP(metaobject protocol) of CLOS. For EIEIO, a simple solution is make
eieio-oref and (setf eieio-oref) a generic
> I haven't gotten around to ask for the latter so far because as long as
> `closql' supports older Emacs releases it would have to keep doing
> something like the former for their benefit anyway.
I think Emacs maintainers can publish a new version of EIEIO in GNU ELPA for
older Emacs releases, just like they did for cl-generic and seq
next prev parent reply other threads:[~2020-05-07 14:52 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-06 4:17 Slot accessing issues in EIEIO Zhu Zihao
2020-05-06 13:28 ` Stefan Monnier
2020-05-06 14:28 ` Zhu Zihao
2020-05-06 21:58 ` Stefan Monnier
2020-05-07 3:20 ` Zhu Zihao
2020-05-07 3:39 ` Stefan Monnier
2020-05-07 4:00 ` Zhu Zihao
2020-05-07 4:55 ` Zhu Zihao
2020-05-07 12:11 ` Stefan Monnier
2020-05-07 14:13 ` Jonas Bernoulli
2020-05-07 14:52 ` Zhu Zihao [this message]
2020-05-07 14:52 ` Stefan Monnier
2020-05-08 3:12 ` Zhu Zihao
2020-05-08 3:48 ` Stefan Monnier
2020-05-08 9:12 ` Zhu Zihao
2020-05-08 15:09 ` Stefan Monnier
2020-05-07 12:15 ` Stefan Monnier
2020-05-07 14:16 ` Jonas Bernoulli
2020-05-07 13:44 ` Jonas Bernoulli
2020-05-08 2:09 ` Stefan Monnier
2020-05-06 15:44 ` Jonas Bernoulli
2020-05-06 15:56 ` Stefan Monnier
2020-05-06 16:43 ` Jonas Bernoulli
2020-05-06 17:06 ` Eric Abrahamsen
2020-05-07 19:32 ` Daniel Colascione
2020-05-06 15:40 ` Jonas Bernoulli
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=87zhajg5m7.wl-all_but_last@163.com \
--to=all_but_last@163.com \
--cc=emacs-devel@gnu.org \
--cc=jonas@bernoul.li \
--cc=monnier@iro.umontreal.ca \
/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).