Re: mysterious threads::shared behaviour

threads::shared uses a mechanism similar to tying, so if you do $x = $h{$_}, then $x isn't a reference to a hash, its a reference to an 'LV' scalar variable, who's action on being accessed is to call the appropriate method that gets or stores a value in the real shared hash (with suitable locking). These LV scalars are temporaries created on demand and freed when no longer used, so you are likely to see address re-use.

Dave.

Comment on Re: mysterious threads::shared behaviour

Replies are listed 'Best First'.
Re^2: mysterious threads::shared behaviour by ericatkin (Novice) on Jan 21, 2009 at 20:22 UTC
So, that explains it. Thank you. I worked around the XML::Dumper issue with the following code: `my %tmp_h; for (keys(%h)) { $tmp_h{$_} = {}; %{$tmp_h{$_}} = %{$h{$_}}; } pl2xml(\%tmp_h, 'h.xml'); %tmp_h = ();` [download] Where can I read more about LV scalars?	[reply] [d/l]
Re^3: mysterious threads::shared behaviour by BrowserUk (Patriarch) on Jan 21, 2009 at 20:54 UTC
Where can I read more about LV scalars? Try PerlGuts Illustrated as a starting point. Search down for "SvPVLV" for the explanation for LV scalars, though you'll probably need to go back to the top and read down to understand the information presented under that heading. Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error. "Science is about questioning the status quo. Questioning authority". In the absence of evidence, opinion is indistinguishable from prejudice. "Too many [] have been sedated by an oppressive environment of political correctness and risk aversion."	[reply]


Don't ask to ask, just ask
	PerlMonks