From: "Basil L. Contovounesios" <contovob@tcd.ie>
To: Jonas Bernoulli <jonas@bernoul.li>
Cc: emacs-devel@gnu.org
Subject: Re: Un-deprecating oset
Date: Tue, 05 May 2020 12:11:00 +0100 [thread overview]
Message-ID: <87imhaljqz.fsf@tcd.ie> (raw)
In-Reply-To: <87eery1xhe.fsf@bernoul.li> (Jonas Bernoulli's message of "Tue, 05 May 2020 12:34:37 +0200")
Jonas Bernoulli <jonas@bernoul.li> writes:
> TL;DR
>
> Deprecating (oref object slot value)
> in favor of (setf (oref object slot) value)
> does *nothing* to increase "namespace sanity", the declared goal.
> It does however take away the programmers choice whether to use
> `setf' or not, but only when it comes to OOP, which seems unfair.
>
> --
> Jonas
>
> PS: I am mostly AFK today. Posting this now anyway because follow
> up actions are already being carried out.
Sorry, I haven't been following the namespace discussions and my only
intention in [1] was to get Emacs building cleanly again. I'll hold off
on pushing that for now.
[1]: https://lists.gnu.org/archive/html/emacs-devel/2020-05/msg00630.html
Two notes I can offer after putting that patch together:
1. While oref has been setf-able for a while, oref-default is not. So
Elisp libraries won't be able to write (setf (oref-default ...) ...)
until Emacs 28 at the earliest.
2. As the patch indicates, oset is used *a lot*.
--
Basil
next prev parent reply other threads:[~2020-05-05 11:11 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-05 10:34 Un-deprecating oset Jonas Bernoulli
2020-05-05 10:48 ` Philippe Vaucher
2020-05-05 11:11 ` Basil L. Contovounesios [this message]
2020-05-05 14:50 ` Stefan Monnier
2020-05-12 15:06 ` Jonas Bernoulli
2020-05-12 16:49 ` Philippe Vaucher
2020-05-12 21:47 ` Adam Porter
2020-05-13 13:04 ` Philipp Stephani
2020-05-14 7:50 ` Juanma Barranquero
2020-05-14 12:13 ` Basil L. Contovounesios
2020-05-14 12:31 ` Juanma Barranquero
2020-05-17 21:19 ` Jonas Bernoulli
2020-05-24 20:09 ` Jonas Bernoulli
2020-05-25 15:21 ` Eli Zaretskii
2020-05-25 16:06 ` Stefan Monnier
2020-05-25 16:25 ` Eli Zaretskii
2020-06-03 14:03 ` Basil L. Contovounesios
2020-06-03 17:03 ` Basil L. Contovounesios
2020-06-06 7:38 ` Eli Zaretskii
2020-06-06 16:43 ` Basil L. Contovounesios
2020-06-08 12:42 ` Jonas Bernoulli
2020-05-25 17:27 ` 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=87imhaljqz.fsf@tcd.ie \
--to=contovob@tcd.ie \
--cc=emacs-devel@gnu.org \
--cc=jonas@bernoul.li \
/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).