From: Kevin Ryde <user42@zip.com.au>
Cc: guile-user@gnu.org, guile-devel@gnu.org
Subject: Re: About removing the low level thread API
Date: Fri, 04 Mar 2005 11:48:22 +1100 [thread overview]
Message-ID: <87k6oo2q3t.fsf@zip.com.au> (raw)
In-Reply-To: <ljis48ya48.fsf@troy.dt.e-technik.uni-dortmund.de> (Marius Vollmer's message of "Thu, 03 Mar 2005 17:20:23 +0100")
Marius Vollmer <marius.vollmer@uni-dortmund.de> writes:
>
> Guile needs it internally anyway, but when we do not export it, we can
> just implement what we need and can change it at will, of course.
I'd be inclined to leave it out for now, wait until the threading
changes have settled down.
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-user
next prev parent reply other threads:[~2005-03-04 0:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-03 16:20 About removing the low level thread API Marius Vollmer
2005-03-04 0:48 ` Kevin Ryde [this message]
2005-04-18 22:51 ` Kevin Ryde
2005-04-19 21:30 ` Rob Browning
2005-04-20 22:35 ` 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=87k6oo2q3t.fsf@zip.com.au \
--to=user42@zip.com.au \
--cc=guile-devel@gnu.org \
--cc=guile-user@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).