Ah yes, I forgot about that. Revised answer:

Syntax. async is shorter, and it simply pass args via capture. That's good, because passing args to a thread as arguments is known to be problematic*.

Without args: 

async(\&process);
async { process(); };
thread->create(\&process);

[download]

With args: 

async(\&process, $arg);           # Safe??
thread->create(\&process, $arg);  # Safe??

async { process($arg); };
thread->create(sub { process($arg) });

[download]

* — The stack isn't ref-counted, and this causes issues when thread creation attempts to clone the variables. I can't remember the exact scenario, but I can look it up if you want more info.

In reply to Re^4: wait for threads to end in parallel by ikegami
in thread wait for threads to end in parallel by pmarcoen

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.