I responded to your points. I'm guessing now you wanted me to enumerate some specific problem case I ran into with iThreads. The problems were several (and sometimes dramatic) but none recent. I don't have any handy. I already said I'd try iThreads again on Windows at some point so if you want to paint me as throwing FUD at iThreads, have as much fun as you want with that.

You started the "I'm anti" "rant" and even promoted it into its own thread so moaning now about having to put up with opposing viewpoints is rather sad.

Perhaps you have little experience with programming with real threads so much of my exposition is foreign to you? That part is somewhat tangential to scripting with "current" Perl.

I was speaking in favor of using coroutines and contrasting that approach with other routes that are more commonly (IME) taken instead of late (not just when using Perl). The prior instability of iThreads surely can't have been a mystery to you but also is of little import in what I wrote. (Though, I suspect that, having had to learn the work-arounds early on, you were also less aware how long the embarrassing ease of finding major bugs persisted.)

In one paragraph I juxtaposed talk of iThreads with talk of real threads which was unfortunate and easily confusing. iThreads are of no interest in the primary cases that lead to me considering Coro because the motivation is reducing process overhead and iThreads add more overhead than fork() would. Their prior instability matters not nor does their lack of deadlocks, only their bloatedness compared to plain old fork() (or just spawning).

If your "No real desire to discuss the issues" is only in regard to prior bugs in iThreads, then it is unfortunate that you missed almost completely the point and have no interest in discussing any of the other "issues".

- tye        

In reply to Re^9: Your main event may be another's side-show. (Coro) by tye
in thread Your main event may be another's side-show. by BrowserUk

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.