Re: advisory lock status when calling a function, with use strict

I don't know anything about lock, but I do know that there is no way strict would have anything to do with lock

In the code you've shown you only have the main thread, so lock is irrelevant

Yes, the lock is still on for the duration of the scope, the documentation is clear about this , threads::shared#lock

Comment on Re: advisory lock status when calling a function, with use strict

Replies are listed 'Best First'.
Re^2: advisory lock status when calling a function, with use strict by ISAI student (Scribe) on Jan 01, 2013 at 07:36 UTC
After reading for the 10th time, I have the answer (although not a direct one): "calls to lock by the same thread from within dynamically nested scopes are safe -- the variable will remain locked until the outermost lock on the variable goes out of scope." The answer is yes.	[reply]