in reply to Re^5: is ||= threadsafe?
in thread is ||= threadsafe?

As I understood things, tye and you said Perl did the locking for the programmer when it came to the state of the SV. . Now you're saying I need to take locks myself.

Now who being ... What was that word you called me?

Perl takes care of protecting any internal changes.

Ie. refcounts; flags; SV upgrades; UTF upgrades; anything that is not (normally) changed directly by the programmer.

Eg, all 3 things you cited in your original post and many more.

The programmer is responsible for locking the variable itself.

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.
RIP an inspiration; A true Folk's Guy

Replies are listed 'Best First'.
Re^7: is ||= threadsafe?
by ikegami (Patriarch) on Oct 25, 2010 at 21:59 UTC

    Now who being ... What was that word you called me?

    If I don't get it, then I can't possibly be playing dumb.

[reply]
      If I don't get it, then I can't possibly be playing dumb.

      {Sigh} Ditto when the "one" you "wasted enough time with" doesn't exist. (Can we can the you said/I said stuff please?)

      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.
[reply]

In Section Seekers of Perl Wisdom