From: Matt Hellige <matt@immute.net>
Subject: Re: Continuations: possible newbie question
Date: Wed, 18 Dec 2002 20:42:29 -0600 [thread overview]
Message-ID: <20021218204229.A26447@metro.immute.net> (raw)
In-Reply-To: <87n0n2hmbv.fsf@zagadka.ping.de>; from mvo@zagadka.ping.de on Thu, Dec 19, 2002 at 01:41:24AM +0100
[Marius Vollmer <mvo@zagadka.ping.de>]
> Matt Hellige <matt@immute.net> writes:
>
> > On the other hand, I'll probably still not end up using this technique
> > to implement my call-backs, given the performance penalties and so on.
> > I hope I can just shuffle things around a bit in my native code...
>
> I would not worry about performance too early. If you invoke one
> continuation for every key press by the user, that should be no
> problem.
Always good advice, of course. In fact I have implemented it that way
for now. In the end, I think performance will be less of a concern for
me than reliability. I admit that I am still somewhat suspicious of
non-linear continuations and C code... :)
So it may change in the future, but for now with my newly rebuilt
libguile, it works like a charm exactly as we've discussed. Thanks all
for your help and advice.
Matt
--
Matt Hellige matt@immute.net
http://matt.immute.net
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-user
next prev parent reply other threads:[~2002-12-19 2:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-18 17:27 Continuations: possible newbie question Thien-Thi Nguyen
2002-12-18 18:14 ` Matt Hellige
2002-12-18 20:04 ` Neil Jerram
2002-12-18 23:51 ` Matt Hellige
2002-12-19 0:41 ` Marius Vollmer
2002-12-19 2:42 ` Matt Hellige [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-12-18 18:42 Thien-Thi Nguyen
2002-12-18 0:14 Matt Hellige
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/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20021218204229.A26447@metro.immute.net \
--to=matt@immute.net \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).