Re: srfi-18 requirements

[Julian Graham]

Any updates on this?  I know you guys are busy with the repository,
but I'm pretty close to having the Scheme implementation for SRFI-18
finished.  Like I said, I think enabling scm_mutex_owner would allow
me to proceed, but I don't want to un-ifdef it without knowing why it
was disabled in the first place (the ChangeLogs don't shed any light
on the matter).

(From a theoretical standpoint, I don't see a problem with the
existence of something like scm_mutex_owner.  The man page for
pthread_mutex_lock claims that it's not part of the pthreads spec
because it could cause an unacceptable performance hit, but it's
pretty clear from playing around with gdb that Linux's pthreads
implementation stores the requisite information...)


>  Speaking of which, though, I've already run into some difficulty
>  implementing mutex-state -- the solution you proposed earlier depends
>  on mutex-owner being visible to Scheme code (it's not, at the moment),
>  and I can't figure out how to write mutex-state efficiently without it
>  (or some other way of passively inspecting the mutex).  Any
>  suggestions would be appreciated!