[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Shrinking the C core
From: |
Eric S. Raymond |
Subject: |
Re: Shrinking the C core |
Date: |
Wed, 9 Aug 2023 12:11:21 -0400 |
Eli Zaretskii <eliz@gnu.org>:
> For veteran and stable code such as this one, we should not rewrite
> them in Lisp just because we can. We should have much more serious
> and good reasons for such changes.
Well, that's awkward. I think I have a serious and good reason to
shrink the core as much as possible, but it's one I'm not yet prepared
to talk about because I don't want to over-promise. I was hoping I
could sneak up on it with a bunch of safe, small changes.
> Even the simple change you did a few days ago broke the build
> on one system and raised a couple of issues some of which are not yet
> resolved, and others we don't even have a good way of resolving except
> by bracing for bug reports.
I want to understand the failure better, then, so I can avoid
repeating it. What build broke, and how? What remaining issues are
there?
(I did of course test te chane with a make bootstrap.)
> So please let's not do that without such reasons.
Noted.
--
<a href="http://www.catb.org/~esr/">Eric S. Raymond</a>
- Re: Type declarations in Elisp, (continued)
- Re: Shrinking the C core, Aurélien Aptel, 2023/08/18
- Re: Shrinking the C core, Emanuel Berg, 2023/08/19
- Re: Shrinking the C core, Richard Stallman, 2023/08/13
- Re: Shrinking the C core, Emanuel Berg, 2023/08/14
- Re: Shrinking the C core, Ihor Radchenko, 2023/08/14
Re: Shrinking the C core, Eli Zaretskii, 2023/08/09
- Re: Shrinking the C core,
Eric S. Raymond <=
Re: Shrinking the C core, Gerd Möllmann, 2023/08/13
Re: Shrinking the C core, Gerd Möllmann, 2023/08/13
Re: Shrinking the C core, Gerd Möllmann, 2023/08/13