[EMAIL PROTECTED] wrote:
Brian:
Starting Thread Test
This is the child thread (0 sec)
This is the main thread (1 sec)
This is the main thread (2 sec)
This is the child thread (2 sec)
This is the main thread (3 sec)
This is the main thread (4 sec)
This is the child thread (4 sec)
This is
[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote:
I thought about the locking approach, but this will all eventually be
wrapped into a Windows services tool that will shutdown the service
gracefully.
I don't see how that removes the need for locking when changing shared
variables?
The
Brian Raven wrote:
use vars qw ($counter $thr $thread $threads);
Prefer declare variables lexically (i.e. my ...), unless you actually
need to do otherwise.
Me too.
# Asynchronously join threads.
$threads = threads-list();
Note that $threads contains a single thread object ...
Bill Luebkert wrote:
Brian Raven wrote:
use vars qw ($counter $thr $thread $threads);
Prefer declare variables lexically (i.e. my ...), unless you actually
need to do otherwise.
Me too.
# Asynchronously join threads.
$threads = threads-list();
Note that $threads contains a
[EMAIL PROTECTED] wrote:
Hi All,
I'm attempting to use the 'threads' module in ActivePerl 5.8.0 build
805.
Everything seems to work until I attempt to shut the process down
gracefully. When I call is_running() the whole thing crashes with
the following output (main thread starts the
Yes, the threads module comes pre-packaged with ActivePerl, and does not
appear to exist according to PPM, so it's not upgradable without upgrading
ActivePerl, which involves me dealing with company red-tape.
The elusive is_running.al shouldn't need to exist outside of the module
itself. It's
[EMAIL PROTECTED] wrote:
Hi All,
I'm attempting to use the 'threads' module in ActivePerl 5.8.0 build
805. Everything seems to work until I attempt to shut the process down
gracefully. When I call is_running() the whole thing crashes with the
following output (main thread starts the
[EMAIL PROTECTED] wrote:
Yes, the threads module comes pre-packaged with ActivePerl, and does not
appear to exist according to PPM, so it's not upgradable without upgrading
ActivePerl, which involves me dealing with company red-tape.
Think you'll need to upgrade.
The elusive is_running.al
I'd love it if I could just upgrade perl, but corporate bureaucracy sucks
and the new versions need approval for security purposes. I initially
tried it with 5.6.1 with less success, and 5.8.0 seems to be very close
less the is_running issue. All I really need is some way to determine if
the
[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote:
I'd love it if I could just upgrade perl, but corporate bureaucracy
sucks and the new versions need approval for security purposes. I
initially tried it with 5.6.1 with less success, and 5.8.0 seems to
be very close less the is_running issue.
# The following gives an error that is_running.al is missing.
# Tried threads-list (threads::running) to search and compare: gave
# bareword error.
Tried the code on linux, got the same error so activeperl is off the hook.
list should be:
$thr-list()
The perldocs show no is_running method,
Brian:
Starting Thread Test
This is the child thread (0 sec)
This is the main thread (1 sec)
This is the main thread (2 sec)
This is the child thread (2 sec)
This is the main thread (3 sec)
This is the main thread (4 sec)
This is the child thread (4 sec)
This is the main thread (5 sec)
This is the
I thought about the locking approach, but this will all eventually be
wrapped into a Windows services tool that will shutdown the service
gracefully.
The way services work, the process needs to ping the service control
manager once in a while when it is still running. So, if a thread didn't
13 matches
Mail list logo
