http://qs321.pair.com?node_id=343737


in reply to Things you need to know before programming Perl ithreads

Well, a COWed approach to shared variables is being considered for Ponie, but that's still at least a year or so in the future. And that doesn't seem to fix the non-shared data copying problem when a thread is started.

I think you meant a COWed approach to non-shared variables, and in fact that should fix the data copying problem.

-- Jamie Lokier

  • Comment on Re: Things you need to know before programming Perl ithreads

Replies are listed 'Best First'.
Re: Re: Things you need to know before programming Perl ithreads
by liz (Monsignor) on Apr 08, 2004 at 21:08 UTC
    Actually, it would have been more correct to remove "shared" in this context. A non-shared variable is cloned when a thread is started. However, a shared variable is also cloned. 
    use threads;
use threads::shared;
my $foo : shared;
print "outside thread: foo = ".(\$foo)."\n";
threads->new( sub { print "inside thread: foo = ".(\$foo)."\n" } )->jo
+in;
__END__
outside thread: foo = SCALAR(0x107cc0)
inside thread: foo = SCALAR(0x232800)

    [download]
    Remember, a shared variable is nothing other than an ordinary tied variable, and cloned as any other variable when a thread is started. Whenever a thread accesses the value of a shared variable, its value is copied from the hidden shared variables thread into the thread local copy, and then presented to the outside world as a "normal" variable. Whenever a thread updates a shared variable, the value is updated in the thread local version, as well as in the hidden shared variables thread.

    All of these copy actions should be COWed, ideally.

    Hope this made sense.

    Liz

[reply]
[d/l]

In Section Meditations