From: Neil Jerram <neil@ossau.uklinux.net>
Cc: Eric Hanchrow <offby1@blarg.net>, bug-guile@gnu.org
Subject: Re: no output from ice-9 `format' after `make-thread'
Date: 04 Nov 2002 18:52:02 +0000 [thread overview]
Message-ID: <m3y989xj59.fsf@laruns.ossau.uklinux.net> (raw)
In-Reply-To: <87znsrcyj0.fsf@zagadka.ping.de>
>>>>> "Marius" == Marius Vollmer <mvo@zagadka.ping.de> writes:
Marius> Note also that (ice-9 format) is not thread safe...
And also -- if it makes any difference -- not async safe. I saw an
interesting bug the other day when GC happened somewhere in the middle
of (ice-9 format), and then:
GC -> after-gc-hook -> something that calls format again.
It wasn't happy about it.
Marius> (which I'm going to fix soonish (when nothing preempts
Marius> me)).
<groan>
Neil
_______________________________________________
Bug-guile mailing list
Bug-guile@gnu.org
http://mail.gnu.org/mailman/listinfo/bug-guile
next prev parent reply other threads:[~2002-11-04 18:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-02 22:59 no output from ice-9 `format' after `make-thread' Eric Hanchrow
2002-11-03 0:00 ` Marius Vollmer
2002-11-04 18:52 ` Neil Jerram [this message]
2002-11-17 15:00 ` 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=m3y989xj59.fsf@laruns.ossau.uklinux.net \
--to=neil@ossau.uklinux.net \
--cc=bug-guile@gnu.org \
--cc=offby1@blarg.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).