in reply to Re: threads::shared: lock a VARIABLE
in thread threads::shared: lock a VARIABLE

So that's how it is, it will waiting for that.
I changed the code like this:

#!/usr/bin/perl use utf8; use feature qw( say ); use threads; use threads::shared; use Data::Dumper; use Storable qw ( freeze thaw ); my $Clock = threads-> new( {'context' => 'void'}, sub { my $count = 0; while(1){ say "programs implemented {$count} sec"; sleep 1; $count += 1; } } ); my $LockVar :shared; $LockVar = "default"; my $LockArray :shared; $LockArray = qw( You cannot lock the individual elements of a cont +ainer variable ); $Lock3Sec = threads->new( {'void' => 'void'}, sub { { say "the lock var default value is {$LockVar}"; lock($LockVar) or warn "cannot lock the var because {$ +!}\n"; sleep 3; say $LockVar; } }, ); $TryToReadLockVar = threads->new( {'void' => 'void'}, sub { my $count = 1; LINE: while( $LockVar eq 'default'){ say "try to modify the Lock var {$count} time"; $count += 1; $LockVar = 'this lock var has been change' or redo LIN +E; say "modify done"; } }, ); $TryToReadLockVar->join(); $Lock3Sec->detach(); $Clock->detach(); sleep 3;

And the output is:

programs implemented {0} sec the lock var default value is {default} try to modify the Lock var {1} time modify done programs implemented {1} sec programs implemented {2} sec programs implemented {3} sec this lock var has been change

It doesn't seem like waiting properly
The previous version of the program was all over in less than a second!
Why it did not wait for the $Lock3Sec for three seconds, just unblock him $LockVar?
Or It kill $Lock3Sec?

Replies are listed 'Best First'.
Re^3: threads::shared: lock a VARIABLE
by Corion (Patriarch) on Aug 23, 2016 at 09:54 UTC

    Where in your code are you checking for whether the variable is locked or not? The locking is "advisory", that means you need to manually check for whether a variable is locked or not. See threads::shared. You need to call lock wherever you want to modify $LockVar:

    async { lock $LockVar; $LockVar = 'Haha'; sleep 3; print "Thread 1 +: $LockVar\n" }; async { lock $LockVar; $LockVar = 'Hehe'; sleep 3; print "Thread 2 +: $LockVar\n" };

    Personally, I try to stay away from approaches that require locks. Usually, a queue into which I can put new values and a single thread that reads from that queue and updates the master data at opportune times is sufficient. Or simply using a relational database as backend, as that takes care of the consistency for me. But if you're using threads, you most likely did so in the hope of gaining performance with short-lived calculations, which talking to a database usually precludes.

    Update: Here is how the locking could work in a self-contained example:

    #!perl -w use strict; use 5.010; use threads; use threads::shared; my $LockVar :shared; $LockVar = 'default'; async { lock $LockVar; my $oldLockVar= $LockVar; $LockVar = 'Haha'; sl +eep 3; say "Thread 1: set var from $oldLockVar to $LockVar" }; async { lock $LockVar; my $oldLockVar= $LockVar; $LockVar = 'Hehe'; sl +eep 5; say "Thread 2: set var from $oldLockVar to $LockVar" }; my $TryToReadLockVar = threads->new( {'void' => 'void'}, sub { my $count = 1; while( 1 ) { say "try to modify the Lock var {$count} time"; $count += 1; lock($LockVar); # !!! say "Now setting LockVar"; $LockVar = 'this lock var has been change'; last; } }, ); $TryToReadLockVar->join(); say "LockVar is now $LockVar"; __END__ try to modify the Lock var {1} time Thread 1: set var from default to Haha Thread 2: set var from Haha to Hehe Now setting LockVar LockVar is now this lock var has been change Perl exited with active threads: 0 running and unjoined 2 finished and unjoined 0 running and detached