From: Eric Abrahamsen <eric@ericabrahamsen.net>
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: Wed, 06 May 2020 10:06:25 -0700 [thread overview]
Message-ID: <87k11pj8mm.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <87v9l9ypyc.fsf@bernoul.li> (Jonas Bernoulli's message of "Wed, 06 May 2020 18:43:07 +0200")
Jonas Bernoulli <jonas@bernoul.li> writes:
> Stefan Monnier <monnier@iro.umontreal.ca> writes:
>
>>>>> Recently, I'm reading the source of
>>>>> closql(https://github.com/emacscollective/closql), A Emacs sqlite database ORM
>>>>> package. It use eieio object, and put a piece of advice on eieio-oref to
>>>>> intercept the reading slot action.
>>>>
>>>> Yuck! Can you explain why they need an advice on `eieio-oref`?
>>>
>>> A right. That's one of the reasons I never bothered to get eieio
>>> changed to better accommodate my extension; I expected a negative
>>> reaction like this.
>>
>> Note the "Yuck" is about putting an advice on such a core function.
>> Not about the functionality that it provides (over which I don't have
>> an opinion yet since I don't know what it does).
>>
>> IOW the "yuck" is saying "please request an extension so it can be
>> better accomodated" ;-)
>
> Okay understood. I guess I was feeling a bit insecure about having
> written a ORMish thing in first place, and was a bit over sensitive
> because of that. ;D
I would love to see this implemented, so I hope our collective
insecurities do not hinder us :)
I would use this, and have considered writing something similar, and am
very, very glad I won't have to.
next prev parent reply other threads:[~2020-05-06 17:06 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
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 [this message]
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=87k11pj8mm.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--cc=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).