Re^2: Threads inside Objects & Sharing

Thank you very much. Mario's idea is the solution for me. I just removed the x1 from the "create" call and changed the name to "__test__" to make it look more private. Passing only $self to the "test" routine is sufficient.

The reply about returning values is interesting as well, but it won't work in my application. The code I posted here is missing the work actually being done by the "test" routine, it's a bit more than "sleep 10". ;-) The procedure will start another application that will report a ready state after some time and then continue until it gets terminated. The "waiter" will have to wait for this ready state, not the end of the thread.

Comment on Re^2: Threads inside Objects & Sharing

Replies are listed 'Best First'.
Re^3: Threads inside Objects & Sharing by Anonymous Monk on Nov 30, 2019 at 21:21 UTC
changed the name to "__test__" to make it look more private. Forget looks, just do it right :) `my $test = sub { ... }; threads->create( $test, ...` [download] The "waiter" will have to wait for this ready state, not the end of the thread. See Re: Parallel download Tk ( threads Thread::Queue LWP::UserAgent WWW::Mechanize)	[reply] [d/l]