From: Mikael Djurfeldt <djurfeldt@nada.kth.se>
Cc: djurfeldt@nada.kth.se, guile-devel@gnu.org
Subject: Re: crypt mutex
Date: Mon, 23 Feb 2004 20:22:19 -0500 [thread overview]
Message-ID: <xy765dxw9tg.fsf@nada.kth.se> (raw)
In-Reply-To: <87vflxwaaz.fsf@ID-28718.user.uni-berlin.de> (Andreas Voegele's message of "Tue, 24 Feb 2004 02:11:48 +0100")
Andreas Voegele <voegelas@gmx.net> writes:
> I'd also prefer a minimal policy. But what do you do if operating
> system A provides the reentrant function foo_r() while operating
> system B provides foo() only? The Scheme procedure "foo" should
> behave the same on both systems.
>
> I think that there are four options:
>
> 1. Use foo_r() if available, otherwise protect foo() with a mutex
> internally.
>
> 2. Use foo() and tell the user to protect the Scheme procedure in
> threaded programs. It doesn't make sense to use foo_r() in this
> scenario.
>
> 3. Provide two Scheme procedures: "foo" and a thread safe version
> "foo-r". "foo-r" uses foo() and a mutex if foo_r() isn't
> available.
>
> 4. Provide two modules, a normal and a thread safe version. A command
> line switch could be used to request thread safety. IMHO this
> would be useful for stuff like the POSIX and networking procedures.
Of these options I think 3 and 4 would add more complexity than is
payed for, and prefer 1 above 2 if foo_r isn't too uncommon.
M
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2004-02-24 1:22 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 [this message]
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
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=xy765dxw9tg.fsf@nada.kth.se \
--to=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).