This is a copy of the file thread-interface.text in the workbook
module. I will go to Graz tomorrow but if there are any follow-ups on
this post I will try to give some limited replies next week.
[Marius, I apologize for not answering another message from you--will
do that next week as well.]
---
Marius Vollmer <[EMAIL PROTECTED]> writes:
> I want to remove scm_mutex_lock (and all other functions in the
> low-level API) and maybe, just maybe, provide instead
>
> - int scm_p_pthread_mutex_lock (scm_p_pthread_mutex_t *mutex)
> Identical to pthread_mutex_lock on systems with pthreads and
Marius Vollmer <[EMAIL PROTECTED]> writes:
>
> On the other hand, Guile itself both works on systems that do provide
> a pthread API, and on systems that do not. C code written for Guile
> might want to support both cases as well (being properly thread safe
> by default, but still compilable even
Marius Vollmer <[EMAIL PROTECTED]> writes:
>
> Guile needs it internally anyway, but when we do not export it, we can
> just implement what we need and can change it at will, of course.
I'd be inclined to leave it out for now, wait until the threading
changes have settled down.
_
Hi,
I am not completely happy about having removed the low level thread
API.
I do think that it is not the job of Guile to provide such a thing and
I also found its presence to be confusing, when compared with the
'regular' thread API.
On the other hand, Guile itself both works on systems that
