My adversion to your first method is that it doesn't work: 

use threads;;
{ 
    package junk; 
    sub new{bless [], $_[0] }
    sub method{ printf __PACKAGE__ . ": @_" }
}

$o = junk->new;;
async{ sub{ $o->method( qw[ the quick brown fox ] ) } };;
## No output!

async \&junk::method, $o, qw[ the quick brown fox ];;
#outputs
junk: junk=ARRAY(0x1adcdec) the quick brown fox

[download]

Likewise your second: 

... setup as above

async( $obj->can("method"), $obj, qw[ the quick brown fox ] );;
[Type of arg 1 to threads::async must be block or sub {} (not subrouti
+ne entry) at ...

[download]

Either of these do: 

async sub{ $o->method( qw[ the quick brown fox ] ) };;
junk: junk=ARRAY(0x1b7d5a4) the quick brown fox

async{ $o->method( qw[ the quick brown fox ] ) };;
junk: junk=ARRAY(0x1c1b4a4) the quick brown fox

[download]

But I'm not sure that there is any benefit to the extra level of indirection.

In particular, I'm still unsure how usable objects across threads are. They now work for (some) simple cases where they did not in the early days, but I'm still uncertain that they will work properly for all cases. If the object is closed over as in most of the cases above, things seem to function because the object is subject to cloning.

But if you want to pass an object to a thread, where the object was created after the thread was spawned, or even the class was loaded after the thread was spawned, I think you're in for some surprises.

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.
"Too many [] have been sedated by an oppressive environment of political correctness and risk aversion."

In reply to Re^5: Doing two things at once, fork question. (thread + method) by BrowserUk
in thread Doing two things at once, fork question. by mhearse

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.