comment on

See http://search.cpan.org/~jdhedden/threads-shared-1.34/lib/threads/shared.pm#OBJECTS and http://cpansearch.perl.org/src/JDHEDDEN/threads-shared-1.34/examples/class.pl.

In general, I do not advise doing this. If you encounter the limitations of coding your application that way, feel free to come back and we can discuss alternative.

Basically this means putting threading within the object methods, rather than layering your objects across threads. I find this approach is easier to reason about, code and develop--and far more efficient--but it does require approaching your problem space from a different perspective.

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.

RIP an inspiration; A true Folk's Guy

In reply to Re: how to make a module and its methods accessable between paren t and child threads by BrowserUk
in thread how to make a module and its methods accessable between paren t and child threads by Anonymous Monk

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Your skill will accomplish what the force of many cannot
	PerlMonks