unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Spencer Baugh <sbaugh@catern.com>
Cc: Alan Mackenzie <acm@muc.de>,  Eli Zaretskii <eliz@gnu.org>,
	emacs-devel@gnu.org
Subject: Re: Rewriting make-docfile.c in Lisp?
Date: Wed, 05 May 2021 15:08:05 -0400	[thread overview]
Message-ID: <jwv5yzxhuqz.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87r1ilrpnt.fsf@catern.com> (Spencer Baugh's message of "Wed, 05 May 2021 14:39:18 -0400")

>> 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_.

Agreed: I'm generally all for writing ELisp instead of C, but
I wouldn't bother rewriting this code in ELisp, personally.

> I was making a change and found it quite difficult.  I think it would
> be much simpler to change if it was in Lisp.  I admit that since it's
> rarely changed, it may not be worth it.

Maybe if you described the change that motivates your proposal, we'd be
less negative ;-)

>> 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.
> A rewrite in Lisp could also take the opportunity to add parallelization
> and speed it up, if indeed this is a bottleneck for the build.

I don't think it can be sped up by writing it in ELisp (on the contrary).
It could be changed such that `make` can run it in parallel on each
C file, indeed, but it would have to be done well enough to make up for
the slowdown imposed by the ELisp version.


        Stefan




  reply	other threads:[~2021-05-05 19:08 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
2021-05-05 18:39       ` Spencer Baugh
2021-05-05 19:08         ` Stefan Monnier [this message]
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=jwv5yzxhuqz.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=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).