From: Mikael Djurfeldt <mdj@mit.edu>
Cc: djurfeldt@nada.kth.se, guile-devel@gnu.org
Subject: Re: crypt mutex
Date: Mon, 23 Feb 2004 15:01:09 -0500 [thread overview]
Message-ID: <xy7oerpefay.fsf@chunk.mit.edu> (raw)
In-Reply-To: <87znb98v9x.fsf@zagadka.ping.de> (Marius Vollmer's message of "Mon, 23 Feb 2004 20:12:42 +0100")
Marius Vollmer <mvo@zagadka.de> writes:
> can lists be meaningfully made thread safe?
Your general question is very relevant. Regarding this example, my
answer would be that we should limit ourselves to making sure that we
don't get segfault or memory corruption if multiple threads randomly
mutates pairs. If a threaded program needs thread safe (in this case:
mutually exclusive) access to a list data structure, it uses a mutex.
M
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
prev parent reply other threads:[~2004-02-23 20:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-21 0:32 crypt mutex Kevin Ryde
2004-02-21 3:24 ` Mikael Djurfeldt
2004-02-21 3:26 ` Mikael Djurfeldt
2004-02-23 19:15 ` Marius Vollmer
2004-02-21 21:50 ` Kevin Ryde
2004-02-23 19:16 ` Marius Vollmer
2004-02-23 19:12 ` Marius Vollmer
2004-02-23 19:46 ` Mikael Djurfeldt
2004-02-23 19:55 ` Mikael Djurfeldt
2004-02-24 1:11 ` Andreas Voegele
2004-02-24 1:22 ` Mikael Djurfeldt
2004-03-20 22:39 ` Marius Vollmer
2004-03-20 22:51 ` Kevin Ryde
2004-07-23 23:53 ` Kevin Ryde
2004-02-23 20:01 ` Mikael Djurfeldt [this message]
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=xy7oerpefay.fsf@chunk.mit.edu \
--to=mdj@mit.edu \
--cc=djurfeldt@nada.kth.se \
--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).