Re: MPS: struct window, prev_buffers + next_buffers

["Gerd Möllmann" <gerd.moellmann@gmail.com>]

Eli Zaretskii <eliz@gnu.org> writes:

>> But it won't be GC'd anyway, becuase it's marked. And if the buffer in
>> the cons is killed, it remains in the list. That makes no sense to me.
>
> But the code doesn't GC buffers, it just removes them from the
> prev_buffers and next_buffers lists.  If a cons cell of the list is
> marked, removing the buffer (which could subsequently lead to GC'ing
> the buffer) might not be expected by the code which uses data that
> references that buffer, even though the buffer is killed.

You mean the possible change to the cdr of the cons cell could affect
the client? Hm, that could be the reason. Thanks.

I think I'll try to let window-{next,prev}-buffers clean the list
before returning it. It doesn't look like something to me that a weak
vector or something like that could solve. WDYT?