caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Brian Hurt <bhurt@spnz.org>
To: Alex Baretta <alex@barettadeit.com>
Cc: Luca Pascali <pasckosky2000@yahoo.it>, <caml-list@inria.fr>
Subject: Re: [Caml-list] Mutex and posix
Date: Sat, 15 Jan 2005 13:37:33 -0600 (CST)	[thread overview]
Message-ID: <Pine.LNX.4.44.0501151335400.5563-100000@localhost.localdomain> (raw)
In-Reply-To: <41E957C5.6050808@barettadeit.com>

On Sat, 15 Jan 2005, Alex Baretta wrote:

> Luca Pascali wrote:
> > Just a little question, my curiosity about the thread module.
> > 
> > I found in Posix (this is from 'info libc' page on section Mutexes) 
> > these three functions
> > 
> > Function: int pthread_mutex_lock (pthread_mutex_t *mutex))
> > Function: int pthread_mutex_trylock (pthread_mutex_t *MUTEX)
> > Function: int pthread_mutex_timedlock (pthread_mutex_t *MUTEX, const 
> > struct timespec *ABSTIME)
> 
> You can probably simulate the third one fairly well by resorting to 
> Unix.select as a timer, but why in the world would you want to lock for 
> a while and then forget about it?

No, you misunderstand what the function does.  The function won't wait 
more than ABSTIME to acquire the lock.  _mutex_lock() waits forever to get 
the lock, _mutex_trylock doesn't wait at all, and _mutex_timedlock only 
waits so long to get the lock.

Brian



  reply	other threads:[~2005-01-15 19:35 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-12 10:53 Luca Pascali
2005-01-12 15:56 ` [Caml-list] " Xavier Leroy
2005-01-12 17:29   ` Luca Pascali
2005-01-15 17:53     ` Alex Baretta
2005-01-15 17:49 ` Alex Baretta
2005-01-15 19:37   ` Brian Hurt [this message]
2005-01-17  8:52     ` Alex Baretta
2005-01-19  3:31       ` Brian Hurt
2005-01-19  9:34         ` Alex Baretta
2005-01-17 12:33   ` Luca Pascali

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Pine.LNX.4.44.0501151335400.5563-100000@localhost.localdomain \
    --to=bhurt@spnz.org \
    --cc=alex@barettadeit.com \
    --cc=caml-list@inria.fr \
    --cc=pasckosky2000@yahoo.it \
    /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 NNTP newsgroup(s).