From: Andy Wingo <wingo@pobox.com>
To: emacs-devel@gnu.org
Subject: Re: Pushing the `gnus-range-*' functions down into the C layer
Date: Fri, 10 Sep 2010 10:06:18 +0200 [thread overview]
Message-ID: <m3iq2eggzp.fsf@unquote.localdomain> (raw)
In-Reply-To: <m31v939cbb.fsf@quimbies.gnus.org> (Lars Magne Ingebrigtsen's message of "Thu, 09 Sep 2010 17:16:56 +0200")
Hi,
On Thu 09 Sep 2010 17:16, Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
> Would anyone mind if I implemented the `gnus-range-*' functions in C for
> Emacs 24?
Speaking with my Guile maintainer hat on, more C is an evil. Guile was a
slow Scheme so lots of stuff got moved to C, but we still weren't quite
fast enough, and by the time we exhausted our possibilities for C
optimization, we were left with a brittle thing.
Instead the real fix was to improve the language implementation, so it
wasn't so slow. The same thing will be the real fix for Emacs. And now
that things are better in Guile, we are rolling back on the
"C-for-speed", because in many cases it's not faster.
I should say that sometimes C is a necessary evil; but it's an evil
nonetheless. If you can fix this particular case algorithmically, that
would be loads better.
Just my 2 eurocents,
Andy
--
http://wingolog.org/
next prev parent reply other threads:[~2010-09-10 8:06 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-09 15:16 Pushing the `gnus-range-*' functions down into the C layer Lars Magne Ingebrigtsen
2010-09-09 19:01 ` Ted Zlatanov
2010-09-09 21:58 ` Lars Magne Ingebrigtsen
2010-09-09 22:25 ` Ted Zlatanov
2010-09-10 3:24 ` Stephen J. Turnbull
2010-09-10 13:53 ` Ted Zlatanov
2010-09-10 14:01 ` Lars Magne Ingebrigtsen
2010-09-10 14:08 ` Leo
2010-09-10 14:15 ` Lars Magne Ingebrigtsen
2010-09-10 14:19 ` Wojciech Meyer
2010-09-11 9:44 ` Stefan Monnier
2010-09-10 14:18 ` Ted Zlatanov
2010-09-10 14:28 ` Lars Magne Ingebrigtsen
2010-09-10 14:38 ` bignums (was: Pushing the `gnus-range-*' functions down into the C layer) Ted Zlatanov
2010-09-10 15:16 ` Pushing the `gnus-range-*' functions down into the C layer Andreas Schwab
2010-09-10 15:22 ` David Kastrup
2010-09-10 15:26 ` Lars Magne Ingebrigtsen
2010-09-11 9:48 ` Stefan Monnier
2010-09-11 11:57 ` Lars Magne Ingebrigtsen
2010-09-11 15:36 ` Stephen J. Turnbull
2010-09-11 15:51 ` Lars Magne Ingebrigtsen
2010-09-11 16:15 ` Wojciech Meyer
2010-09-12 9:57 ` Stefan Monnier
2010-09-10 19:28 ` Tom Tromey
2010-09-14 15:52 ` Ted Zlatanov
2010-09-11 5:52 ` Stephen J. Turnbull
2010-09-13 11:45 ` Eli Zaretskii
2010-09-09 22:21 ` Wojciech Meyer
2010-09-09 23:48 ` Ted Zlatanov
2010-09-09 23:56 ` Wojciech Meyer
2010-09-10 0:07 ` Lars Magne Ingebrigtsen
2010-09-10 0:17 ` Wojciech Meyer
2010-09-10 8:06 ` Andy Wingo [this message]
2010-09-10 10:20 ` Wojciech Meyer
2010-09-10 10:43 ` Stefan Monnier
2010-09-10 12:35 ` Lars Magne Ingebrigtsen
2010-09-10 12:49 ` rfc2047-decode-string in C? Lars Magne Ingebrigtsen
2010-09-10 13:47 ` Stefan Monnier
2010-09-10 13:51 ` Lars Magne Ingebrigtsen
2010-09-11 16:10 ` Lars Magne Ingebrigtsen
2010-09-10 13:07 ` Pushing the `gnus-range-*' functions down into the C layer joakim
2010-09-10 13:22 ` Lars Magne Ingebrigtsen
2010-09-10 13:45 ` Stefan Monnier
2010-09-10 14:01 ` Ted Zlatanov
2010-09-10 14:09 ` Lars Magne Ingebrigtsen
2010-09-11 9:36 ` Stefan Monnier
2010-09-10 14:06 ` Lars Magne Ingebrigtsen
2010-09-11 3:18 ` Daniel Pittman
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=m3iq2eggzp.fsf@unquote.localdomain \
--to=wingo@pobox.com \
--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).