From: Marius Vollmer <mvo@zagadka.ping.de>
Subject: C level mutices and condition variables
Date: 26 Oct 2002 22:12:25 +0200 [thread overview]
Message-ID: <87vg3pot7a.fsf@zagadka.ping.de> (raw)
Hi,
currently, we support the scm_t_mutex and scm_t_cond types, along with
some functions. You can declare a variable of type scm_t_mutex and
initialize it with scm_mute_init, for example.
This makes it hard to have SCM data in a scm_t_mutex since you have to
protect it without the help from the user of the mutex. Also, this is
not 'astract' enough when we make thread package support a run-time
option (which we should).
Dirk did some work in this direction in the dirk-thread-factorization
branch. I propose something simpler:
Let's just remove C level support for mutex and condition variable
objects and tell them to use the Scheme level mutices, which are also
available to C. (With deprecation.)
Ok?
--
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-10-26 20:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-26 20:12 Marius Vollmer [this message]
2002-10-26 21:28 ` C level mutices and condition variables Neil Jerram
2002-10-26 23:33 ` Marius Vollmer
2002-10-27 7:40 ` Neil Jerram
2002-10-27 12:37 ` Marius Vollmer
2002-11-11 22:05 ` Thread interface issues (was Re: C level mutices and condition variables) Mikael Djurfeldt
2002-11-12 22:37 ` GC & threads (was: Thread interface issues) Han-Wen Nienhuys
2002-11-12 23:09 ` Thread interface issues (was Re: C level mutices and condition variables) Neil Jerram
2002-11-22 21:27 ` Marius Vollmer
2002-11-23 20:55 ` Thread interface issues Mikael Djurfeldt
2002-11-24 10:27 ` 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=87vg3pot7a.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).