From: "John Wiegley" <johnw@gnu.org>
To: Tom Tromey <tom@tromey.com>
Cc: emacs-devel@gnu.org
Subject: Re: An idea, now that we have dynamic loading
Date: Mon, 14 May 2018 16:36:58 -0700 [thread overview]
Message-ID: <m2d0xxstb9.fsf@newartisans.com> (raw)
In-Reply-To: <87o9hhhpzk.fsf@tromey.com> (Tom Tromey's message of "Mon, 14 May 2018 15:44:15 -0600")
>>>>> "TT" == Tom Tromey <tom@tromey.com> writes:
TT> Anyway, the backend has some bugs, and it generates "Emacs C core"-style C
TT> code, not "Emacs dynamic module"-style C code.
Could some of our internal C sources be replaced by Emacs Lisp, which the
Makefile would compile into C as part of the regular build process? This would
allow testing using the Emacs Lisp version, with compilation into C for the
sake of performance. And maybe benchmark would even rule out the need to
compile that file in the end...
--
John Wiegley GPG fingerprint = 4710 CF98 AF9B 327B B80F
http://newartisans.com 60E1 46C4 BD1A 7AC1 4BA2
next prev parent reply other threads:[~2018-05-14 23:36 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-06 1:44 An idea, now that we have dynamic loading John Wiegley
2018-05-06 2:25 ` Óscar Fuentes
2018-05-10 12:45 ` Siraphob (Ben) Phipathananunth
2018-05-10 20:31 ` John Wiegley
2018-05-11 6:11 ` Eli Zaretskii
2018-05-11 7:56 ` John Wiegley
2018-05-11 14:59 ` Siraphob (Ben) Phipathananunth
2018-05-11 15:02 ` Eli Zaretskii
2018-05-11 15:22 ` An Emacs benchmarking suite (was: An idea, now that we have dynamic loading) Siraphob (Ben) Phipathananunth
2018-05-11 17:38 ` Eli Zaretskii
2018-05-14 11:37 ` An Emacs benchmarking suite Phillip Lord
2018-05-14 16:18 ` Eli Zaretskii
2018-05-14 16:30 ` Stefan Monnier
2018-05-15 13:24 ` Phillip Lord
2018-05-10 13:58 ` An idea, now that we have dynamic loading Tom Tromey
2018-05-10 20:31 ` John Wiegley
2018-05-14 21:44 ` Tom Tromey
2018-05-14 23:36 ` John Wiegley [this message]
2018-05-21 21:13 ` Tom Tromey
2018-05-22 3:23 ` John Wiegley
2018-05-22 4:20 ` Tom Tromey
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m2d0xxstb9.fsf@newartisans.com \
--to=johnw@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=tom@tromey.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.