From: Mikael Djurfeldt <djurfeldt@nada.kth.se>
Cc: djurfeldt@nada.kth.se
Subject: Re: pthread fast mutexes
Date: Mon, 23 Feb 2004 19:02:44 -0500 [thread overview]
Message-ID: <xy7ekslwdi3.fsf@nada.kth.se> (raw)
In-Reply-To: <87oerptl3i.fsf@zip.com.au> (Kevin Ryde's message of "Tue, 24 Feb 2004 09:46:57 +1000")
Kevin Ryde <user42@zip.com.au> writes:
> Mikael Djurfeldt <mdj@mit.edu> writes:
>>
>> make-mutex --> make-fast-mutex
>> make-fair-mutex --> make-mutex
>
> That might be prudent if in the past make-mutex had been safe to
> various abuses.
Well, but the past mutexes didn't report an error either. I've not
taken away any semantics.
_______________________________________________
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 0:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-23 21:16 pthread fast mutexes Kevin Ryde
2004-02-23 22:05 ` Mikael Djurfeldt
2004-02-23 22:22 ` Mikael Djurfeldt
2004-02-23 23:46 ` Kevin Ryde
2004-02-24 0:02 ` Mikael Djurfeldt [this message]
2004-02-28 20:18 ` Kevin Ryde
2004-03-20 22:51 ` Marius Vollmer
2004-02-23 22:33 ` Kevin Ryde
2004-02-24 1:17 ` Mikael Djurfeldt
2004-03-20 22: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=xy7ekslwdi3.fsf@nada.kth.se \
--to=djurfeldt@nada.kth.se \
/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).