From: Clinton Ebadi <clinton@unknownlamer.org>
Subject: Re: threadsafe format.scm
Date: Thu, 31 Jul 2003 23:18:59 -0400 [thread overview]
Message-ID: <200307312318.59107.clinton@unknownlamer.org> (raw)
In-Reply-To: <200307312239.32519.clinton@unknownlamer.org>
> I'll rework the error-continuation and send a third revision of the patch,
> but I'd like to know if anyone has used the new format and found their
> programs to run slower.
Actually, format:error-continuation isn't used anymore so any references to it
can simply be removed.
--
http://unknownlamer.org
AIM:unknownlamer IRC:unknown_lamer@freenode#hprog
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2003-08-01 3:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-29 3:27 threadsafe format.scm Clinton Ebadi
2003-07-30 22:36 ` Kevin Ryde
2003-07-30 23:06 ` Clinton Ebadi
2003-07-31 2:46 ` Clinton Ebadi
2003-07-31 22:11 ` Kevin Ryde
2003-08-01 2:39 ` Clinton Ebadi
2003-08-01 3:18 ` Clinton Ebadi [this message]
2003-09-15 13:33 ` Marius Vollmer
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=200307312318.59107.clinton@unknownlamer.org \
--to=clinton@unknownlamer.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.
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).