It's compiled to support "ithreads" (interperator threads),
which are currently under development.
The "Thread" module is for 5.005-style threads, which are
not ithreads. 5.005-style threads are being abondoned, apparently
because they create race conditions that cannot be resolved
efficiently. I would advise against their use.
If you are interested,
there is an experimental "threads" module for ithreads
access from perl code.
The primary reason that it has threading support is to support forking emulation, because Windows does not
have a OS-level fork call. (See perlfork.)
You should be able to access threads this way, but beware
that Win32::GUI might have some problems
if you spawn threads while it's objects are in scope
because
it's (XS-based) destructors could be called prematurely, or twice.
update: (These problems may occur if
you merely have such objects in exsitence at time
of forking, even.)
-
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.
|