[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Not protecting Lisp objects from GC
From: |
Gerd Möllmann |
Subject: |
Re: Not protecting Lisp objects from GC |
Date: |
Mon, 27 Jan 2025 14:45:38 +0100 |
User-agent: |
Gnus/5.13 (Gnus v5.13) |
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Stefan Kangas <stefankangas@gmail.com>
>> Date: Mon, 27 Jan 2025 03:46:21 -0600
>>
>> As I said in Bug#75521, I'll reiterate here for the record: I believe we
>> should remove DEFVAR_LISP_NOPRO and avoid pursuing these kinds of
>> optimizations.
>
> And as I said in that bug's discussion, I'm not interested in
> improving the old GC where the existing code works well and is not
> understood very well by the active maintainers.
The effects and unmaintainability of what I referred to it very well
known. One doesn't have to be a rocket engineer to fix these cases.
- Not protecting Lisp objects from GC, Gerd Möllmann, 2025/01/27
- Re: Not protecting Lisp objects from GC, Stefan Kangas, 2025/01/27
- Re: Not protecting Lisp objects from GC, Eli Zaretskii, 2025/01/27
- Re: Not protecting Lisp objects from GC, Gerd Möllmann, 2025/01/27
- Re: Not protecting Lisp objects from GC, Eli Zaretskii, 2025/01/27
- Re: Not protecting Lisp objects from GC, Gerd Möllmann, 2025/01/27
- Re: Not protecting Lisp objects from GC, Eli Zaretskii, 2025/01/27
- Re: Not protecting Lisp objects from GC, Gerd Möllmann, 2025/01/27
- Re: Not protecting Lisp objects from GC, Eli Zaretskii, 2025/01/27
- Re: Not protecting Lisp objects from GC, Gerd Möllmann, 2025/01/27
- Re: Not protecting Lisp objects from GC, Eli Zaretskii, 2025/01/27
- Re: Not protecting Lisp objects from GC, Gerd Möllmann, 2025/01/27