From: Christopher Cramer <crayc@pyro.net>
Cc: guile-devel@gnu.org
Subject: Re: future thread interface
Date: Tue, 1 Jul 2003 13:57:29 -0500 [thread overview]
Message-ID: <20030701135729.A24662@kiwi.pyrotechnics.com> (raw)
In-Reply-To: <87vfumtudg.fsf@zagadka.ping.de>; from mvo@zagadka.de on Tue, Jul 01, 2003 at 12:27:07PM +0200
On Tue, Jul 01, 2003 at 12:27:07PM +0200, Marius Vollmer wrote:
> In my view, the goal is to avoid to have to chose. That is, Guile
> should be written against the POSIX pthread API only. When people
> have a need for a non-standard threading implementation, that
> implementation should offer the pthread API and Guile can then use it
> transparently.
This is a surprising answer, since the code is clearly not written to
only use the pthread API. I suppose the goal has changed, and the code
doesn't reflect that yet.
Does that mean scm_internal_select will be eliminated?
> This depends on what you mean exactly with "coop" threads. The coop
> thread package based on QuickThreads has already been removed from
> 1.7.
So it's not coming back? The only other mention of this I could find was
a ChangeLog entry saying 'Support for "coop" threads has been removed
until I get time to add it again.'
--
Christopher Cramer <crayc@pyro.net> <http://www.pyro.net/~crayc/>
"People said it couldn't be that our soldiers would do such things. Now
you read worse things in the mainstream media and people don't care. We
used to say that if only people know about it, it would stop. Now they
know about it, and it hasn't stopped." - Adam Keller
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2003-07-01 18:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-01 6:32 future thread interface Christopher Cramer
2003-07-01 10:27 ` Marius Vollmer
2003-07-01 18:57 ` Christopher Cramer [this message]
2003-07-05 12:05 ` Mikael Djurfeldt
2003-07-27 16:51 ` 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=20030701135729.A24662@kiwi.pyrotechnics.com \
--to=crayc@pyro.net \
--cc=guile-devel@gnu.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).