From: Alan Mackenzie <acm@muc.de>
To: Spencer Baugh <sbaugh@catern.com>
Cc: Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org
Subject: Re: Rewriting make-docfile.c in Lisp?
Date: Wed, 5 May 2021 17:16:25 +0000 [thread overview]
Message-ID: <YJLS6Zz/QdhJnXDX@ACM> (raw)
In-Reply-To: <87v97xrurb.fsf@catern.com>
Hello, Spencer.
On Wed, May 05, 2021 at 12:49:12 -0400, Spencer Baugh wrote:
> Eli Zaretskii <eliz@gnu.org> writes:
> >> Couldn't this be written in Lisp?
> >
> > make-docfile does several jobs; did you mean to convert them all to
> > Lisp? One of them is globals.h, which is needed for compiling the
> > Emacs C sources.
> Ah, I didn't see that globals.h was generated by make-docfile. I just
> meant generating etc/DOC. Pluss any other jobs done by make-docfile that
> aren't required to compile Emacs, if there are any.
Why would one want to write it in Lisp anyway?
We have a working program in C which requires little maintenance, yet
which is used continually. Rewriting it in Lisp would be _work_.
Also, the Lisp version would run more slowly than the C version, leading
to more irritation over build speeds than there currently is. I think
this is also part of the build which holds things up in a single core,
thus making its speed more important than, say, a C or Lisp compilation.
--
Alan Mackenzie (Nuremberg, Germany).
next prev parent reply other threads:[~2021-05-05 17:16 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-05 15:56 Rewriting make-docfile.c in Lisp? sbaugh
2021-05-05 16:13 ` Eli Zaretskii
2021-05-05 16:49 ` Spencer Baugh
2021-05-05 17:16 ` Alan Mackenzie [this message]
2021-05-05 18:39 ` Spencer Baugh
2021-05-05 19:08 ` Stefan Monnier
2021-05-05 19:13 ` Eli Zaretskii
2021-05-05 19:38 ` Stefan Monnier
2021-05-05 20:05 ` Glenn Morris
2021-05-05 21:18 ` Stefan Monnier
2021-05-05 21:34 ` Stefan Monnier
2021-05-05 21:11 ` Spencer Baugh
2021-05-06 8:45 ` Eli Zaretskii
2021-05-05 19:10 ` Eli Zaretskii
2021-05-05 21:27 ` Spencer Baugh
2021-05-05 18:49 ` 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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YJLS6Zz/QdhJnXDX@ACM \
--to=acm@muc.de \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=sbaugh@catern.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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).