From: Lars Ingebrigtsen <larsi@gnus.org>
To: Matt Armstrong <matt@rfc20.org>
Cc: 46836@debbugs.gnu.org
Subject: bug#46836: 28.0.50; Clean up obsolete comment for unchain_marker
Date: Mon, 01 Mar 2021 14:29:49 +0100 [thread overview]
Message-ID: <87sg5f6lyq.fsf@gnus.org> (raw)
In-Reply-To: <m2czwjdcrg.fsf@matts-mbp-2016.lan> (Matt Armstrong's message of "Sun, 28 Feb 2021 14:54:27 -0800")
Matt Armstrong <matt@rfc20.org> writes:
> I wondered why there was a scare comment for unchain_marker, when the
> code itself did not look like it was especially different from the other
> nearby functions. It turns out that the call into this function from GC
> was removed a few years ago.
[...]
> -/* Remove MARKER from the chain of whatever buffer it is in,
> - leaving it points to nowhere. This is called during garbage
> - collection, so we must be careful to ignore and preserve
> - mark bits, including those in chain fields of markers. */
> +/* Remove MARKER from the chain of whatever buffer it is in. Set its
> + buffer NULL. */
Thanks; applied to Emacs 28.
Looking at the code in unchain_marker, I was a bit confused, because the
code looks very straightforward? I wondered whether the function could
also be simplified now that it doesn't have to preserve mark bits...
But all the special mark bit code was removed from this code a couple
decades ago. :-)
commit 5e097e002ba08205c8a4643b3495dbd45462147f
Author: Stefan Monnier <monnier@iro.umontreal.ca>
AuthorDate: Thu Jun 26 23:17:50 2003 +0000
...
else
- {
- omark = XMARKBIT (XMARKER (prev)->chain);
- XMARKER (prev)->chain = next;
- XSETMARKBIT (XMARKER (prev)->chain, omark);
- }
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
prev parent reply other threads:[~2021-03-01 13:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-28 22:54 bug#46836: 28.0.50; Clean up obsolete comment for unchain_marker Matt Armstrong
2021-03-01 13:29 ` Lars Ingebrigtsen [this message]
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=87sg5f6lyq.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=46836@debbugs.gnu.org \
--cc=matt@rfc20.org \
/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.