in reply to Printing to STDERR causes deadlocks.

Sorry, I couldn't resist (I'm still getting used to this whole anonymous monk thing)...

Shared state concurrency is a no, no

  • Comment on Re: Printing to STDERR causes deadlocks.

Replies are listed 'Best First'.
Re^2: Printing to STDERR causes deadlocks.
by BrowserUk (Patriarch) on Apr 26, 2005 at 21:09 UTC
    I'm still getting used to this whole anonymous monk thing

    Why remain anonymous?

    Anyway, you're kinda making my point for me. Again.

    The point being that it is extremely difficult to do even very, very simple things using the pthreads API--at least, as exposed to Perl through threads. It's too late for Perl 5, but Perl 6 needs something much better.

    It's a little like the difference between the raw sockets calls that perl exposes, and using IO::Socket::INET, except that with for a threading api to be useful within Perl, it need to be architected into the language, declaratively, not bolted through as an after thought.

    I also will contend that native threads alone are not enough, but the arguments supporting that are complex and are taking me some time and a lot of research to put together. Unfortunately, the inadaquacies of threads and the restrictions the implementations impose upon it's use, mean that it is hard to come up with convicing demonstrations of what is possible, and as we've seen, arguments alone are not enough.


    Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
    Lingua non convalesco, consenesco et abolesco.
    Rule 1 has a caveat! -- Who broke the cabal?