From: Richard Stallman <rms@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Compiling byte code to native
Date: Wed, 02 Jun 2004 18:56:13 -0400 [thread overview]
Message-ID: <E1BVeeb-0008Ul-MX@fencepost.gnu.org> (raw)
In-Reply-To: <87u0xuuqvm.fsf@sno.mundell.ukfsn.org> (message from Matthew Mundell on 02 Jun 2004 12:43:41 +0100)
I simply deleted that TODO entry, since it looks like this optimization
isn't worth a big effort. Computers are so fast nowadays that Emacs
Lisp code hardly needs speeding up.
I only regret that you had to spend time on an optimization that turns
out not to be fruitful. Thank you for working on it.
next prev parent reply other threads:[~2004-06-02 22:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-02 11:43 Compiling byte code to native Matthew Mundell
2004-06-02 14:22 ` Stefan Monnier
2004-06-02 16:30 ` Matthew Mundell
2004-06-02 17:04 ` Stefan Monnier
2004-06-02 18:05 ` Matthew Mundell
2004-06-02 22:56 ` Richard Stallman [this message]
2004-06-03 10:32 ` Matthew Mundell
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=E1BVeeb-0008Ul-MX@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=emacs-devel@gnu.org \
/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).