in reply to Re^2: Problems using module Async
in thread Problems using module Async
Thanks for the answer. :) Yes I saw the correction.
I've had a deeper look into perlthrtut meanwhile, too. I think best for me would be a threads->create in combination with detach (since I want a nonblocking behavior for parents's mainloop, where join and also Thread::Queues's dequeue if theres nothing in queue would cause the process to wait, I have tasks that differ a lot in execution time so I want to ensure parent's always in control of what's going on and not "hang" for minutes waiting for child) and share a hash with threads::shared where the thread can report its state and maybe return (simple/non-reference) values to the parent.
Can you confirm that, or is there a better way?
|
|---|
| Replies are listed 'Best First'. | |
|---|---|
|
Re^4: Problems using module Async
by hfi (Novice) on Nov 29, 2015 at 17:17 UTC | |
by BrowserUk (Patriarch) on Nov 29, 2015 at 18:10 UTC |