Beefy Boxes and Bandwidth Generously Provided by pair Networks
more useful options

Re: Threads weirdness

by Corion (Patriarch)
on Jul 06, 2009 at 14:12 UTC ( #777555=note: print w/replies, xml ) Need Help??

in reply to Threads weirdness

Passing around objects among threads is fraught with potential for errors. I think the basic principle is that you'll get a copy unless you declare something as explicitly :shared. See threads and threads::shared. Personally, I'd try to decouple the scheduler from the worker(s) and have a queue in each direction to pass commands forth and receive the status (+data) back from the worker(s).

Replies are listed 'Best First'.
Re^2: Threads weirdness
by reasonablekeith (Deacon) on Jul 06, 2009 at 14:50 UTC
    Thanks Corion,

    The only thing that changes in the component object is the last_run_time value, so I guess you're saying I can handle that in the main thread instead of it being managed by the object, and that might fix my problem?

    I still find it very weird, as (disregarding what's in the object), that scalar ref value changes from one line to the next.

    my name's not Keith, and I'm not reasonable.

Log In?

What's my password?
Create A New User
Domain Nodelet?
Node Status?
node history
Node Type: note [id://777555]
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others scrutinizing the Monastery: (4)
As of 2022-09-28 09:20 GMT
Find Nodes?
    Voting Booth?
    I prefer my indexes to start at:

    Results (124 votes). Check out past polls.