English version
Accueil     À propos     Téléchargement     Ressources     Contactez-nous    

Ce site est rarement mis à jour. Pour les informations les plus récentes, rendez-vous sur le nouveau site OCaml à l'adresse ocaml.org.

Browse thread
Mutex and posix
[ Home ] [ Index: by date | by threads ]
[ Search: ]

[ Message by date: previous | next ] [ Message in thread: previous | next ] [ Thread: previous | next ]
Date: 2005-01-15 (17:49)
From: Alex Baretta <alex@b...>
Subject: Re: [Caml-list] Mutex and posix
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?

Besides --- given Machiavelli works in an asynchronous, event-modeled 
world --- why would want to use synchronous primitives such as timedlock?


Baretta DE&IT
A division of Baretta SRL

tel. +39 02 370 111 55
fax. +39 02 370 111 54

Our technology:

The Application System/Xcaml (AS/Xcaml)

The FreerP Project