Re: GOOPS method cache locking bug?

[Mikael Djurfeldt]

Andreas Rottmann <address@hidden> writes:

> However, I found an inconsitency in the docs (in threads.c) for the
> make-mutex procedure; it says Guile mutexes are always recursive:
>
>   Locking a mutex that a thread already owns will succeed right away
>   and will not block the thread.  That is, Guile's mutexes are
>   @emph{recursive}.
>
> Nevertheless, when doing 
>
> (let ((m (make-mutex))) 
>   (lock-mutex m)
>   (lock-mutex m))
>
>  at the guile prompt, I get a deadlock.

The bug is the docs.  I haven't updated it yet (shame on me).  As
you've discovered, you type make-fair-mutex for recursive (and fair)
mutexes.

Mikael