From: Eli Zaretskii <eliz@gnu.org>
To: Tom Tromey <tom@tromey.com>
Cc: eggert@cs.ucla.edu, robert-emacs@cochranmail.com,
dmantipov@yandex.ru, emacs-devel@gnu.org
Subject: Re: [PATCH] src/process.c: remove unnecessary setters
Date: Fri, 05 Jan 2018 20:23:13 +0200 [thread overview]
Message-ID: <83o9m89nce.fsf@gnu.org> (raw)
In-Reply-To: <87r2r4jih0.fsf@tromey.com> (message from Tom Tromey on Fri, 05 Jan 2018 10:58:19 -0700)
> From: Tom Tromey <tom@tromey.com>
> Cc: Paul Eggert <eggert@cs.ucla.edu>, Eli Zaretskii <eliz@gnu.org>, dmantipov@yandex.ru, emacs-devel@gnu.org
> Date: Fri, 05 Jan 2018 10:58:19 -0700
>
> >>>>> "Robert" == Robert Cochran <robert-emacs@cochranmail.com> writes:
>
> Robert> IMO, there's not much of a point in wrapping something so simple in a
> Robert> funcall. I understand that a good compiler will optimize that away, but
> Robert> that doesn't really fix the code any.
>
> Robert> Whatever reason for leaving these has apparently faded into history, if
> Robert> my past self is to be believed:
>
> IIRC those were introduced to support incremental GC.
Indeed. In general, we have similar setters for window, frame, and
buffer objects. Do we want to get rid of all of those? And if we do,
does that mean we abandon all hope for migrating to a more modern GC?
next prev parent reply other threads:[~2018-01-05 18:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-29 23:30 [PATCH] src/process.c: remove unnecessary setters Robert Cochran
2017-05-29 23:47 ` Paul Eggert
2017-05-30 1:40 ` Robert Cochran
2017-05-30 5:19 ` Paul Eggert
2017-05-30 6:05 ` Eli Zaretskii
2018-01-04 0:42 ` Robert Cochran
2018-01-04 0:44 ` Paul Eggert
2018-01-04 4:39 ` Robert Cochran
2018-01-04 8:06 ` Paul Eggert
2018-01-05 17:58 ` Tom Tromey
2018-01-05 18:23 ` Eli Zaretskii [this message]
2018-01-06 9:37 ` Robert Cochran
2018-01-06 15:03 ` Eli Zaretskii
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83o9m89nce.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=dmantipov@yandex.ru \
--cc=eggert@cs.ucla.edu \
--cc=emacs-devel@gnu.org \
--cc=robert-emacs@cochranmail.com \
--cc=tom@tromey.com \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.