From: Marius Vollmer <mvo@zagadka.ping.de>
Subject: C level threads...
Date: 02 Dec 2002 02:30:37 +0100 [thread overview]
Message-ID: <87u1hx437m.fsf@zagadka.ping.de> (raw)
Ok, I have documented and implemented the C level thread API (mostly
unchanged from what we had before I deprecated it), and reorganized
the thread implementation to revolve around this API. The difference
between null-threads and coop-pthreads (implementation-wise, not
behavior-wise) is now very small, which should be a good thing.
I haven't yet ported coop threads over to the new arrangement, tho,
since I didn't had the time and I wanted to commit what I had anyway.
I will come back to this and reinstall coop support, hopefully soon.
Anyway, the default is now coop-pthreads and I think we should keep it
that way. Threads should not be some thing that you have to configure
into your Guile and where you are lucky that you can get them, they
should be something that is always there (unless configured away).
The C level API is not pluggable yet, and I have to admit that I
didn't plan for that, but the thing is still 'hot' and ductile so if
someone wants to work on pluggable threads...
--
GPG: D5D4E405 - 2F9B BCCC 8527 692A 04E3 331E FAF8 226A D5D4 E405
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next reply other threads:[~2002-12-02 1:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-02 1:30 Marius Vollmer [this message]
2002-12-02 8:24 ` C level threads Mikael Djurfeldt
2002-12-02 11:43 ` Mikael Djurfeldt
2002-12-02 17:27 ` Marius Vollmer
2002-12-02 12:57 ` Mikael Djurfeldt
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=87u1hx437m.fsf@zagadka.ping.de \
--to=mvo@zagadka.ping.de \
/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).