in reply to Re^13: baton passing threads and cond_signal
in thread baton passing threads and cond_signal

If there are problems with pthreads (which I guess perl/windows does not use, but I may be wrong) I would be interested, so go ahead an post away :-)

I've got some other issues with perl threads (I mean, the perl API to threads, not the actual implementation - I don't know enough about that) so maybe I should take some time to write them down too.

"What should it profit a man, if he should win a flame war, yet lose his cool?"
  • Comment on Re^14: baton passing threads and cond_signal

Replies are listed 'Best First'.
Re^15: baton passing threads and cond_signal
by BrowserUk (Patriarch) on Aug 23, 2007 at 22:25 UTC

    The first problem is that I've been playing with the cond_* apis for quite a while now and basically, they do not seem to work properly. As best as I can assertain. But there are precious few examples of their use (from Perl) as far as I can find.

    The second problem is that I am using emulations of those APIs rather than the real thing, so it's not clear to me whether the problems I have had are down to the APIs themselves, the Win32 emulations, or just the sparsity of documentation and my (lack of) understanding of how to use them.

    The piece of the OPs puzzle that is still missing is: does the hang that occurs on single-cpu Win32 also happen on single-cpu Linux? Conversely, does the hang not happen on multi-cpu Win32?

    Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
    "Science is about questioning the status quo. Questioning authority".
    In the absence of evidence, opinion is indistinguishable from prejudice.
[reply]

In Section Seekers of Perl Wisdom