From: pahe@daimi.au.dk (Peter von der Ahé)
Subject: Re: Bug in multipart/alternative
Date: 18 Apr 1999 20:38:59 +0200 [thread overview]
Message-ID: <yc0k8v9wz7g.fsf@ufleku.daimi.au.dk> (raw)
In-Reply-To: Bruce Stephens's message of "18 Apr 1999 12:49:36 +0100"
>>>>> "BS" == Bruce Stephens <bruce@cenderis.demon.co.uk> writes:
BS> Why not? Lisp is good at recursion, after all.
Some Lisp variants are, but not Emacs Lisp, here is a cut from the
Tips section of the elisp info pages:
Tips for Making Compiled Code Fast
Here are ways of improving the execution speed of byte-compiled Lisp
programs.
...
* Use iteration rather than recursion whenever possible. Function
calls are slow in Emacs Lisp even when a compiled function is
calling another compiled function.
Kind Regards
Peter
next prev parent reply other threads:[~1999-04-18 18:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87hfsp969d.fsf@mattdav.vip.best.com>
1999-04-18 11:05 ` Lars Magne Ingebrigtsen
1999-04-18 11:49 ` Bruce Stephens
1999-04-18 18:05 ` Lars Magne Ingebrigtsen
1999-04-18 18:37 ` Bruce Stephens
1999-04-20 13:28 ` Robert Bihlmeyer
1999-06-12 2:22 ` Lars Magne Ingebrigtsen
1999-04-18 18:38 ` Peter von der Ahé [this message]
1999-04-18 19:33 ` Hrvoje Niksic
1999-04-20 4:31 ` François Pinard
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=yc0k8v9wz7g.fsf@ufleku.daimi.au.dk \
--to=pahe@daimi.au.dk \
/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.
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 NNTP newsgroup(s).