Beefy Boxes and Bandwidth Generously Provided by pair Networks
Just another Perl shrine
 
PerlMonks  

Re^4: is ||= threadsafe?

by BrowserUk (Pope)
on Oct 25, 2010 at 04:56 UTC ( #867139=note: print w/replies, xml ) Need Help??


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

segmentation fault, premature deallocation and segmentation fault (respectively)

I challenge you to demonstrate any one of those.

And when you can't, come back and I'll explain why you can't.

Replies are listed 'Best First'.
Re^5: is ||= threadsafe?
by ikegami (Pope) on Oct 25, 2010 at 05:03 UTC

    Well, a refcount increase is an increment, and increment operations aren't necessarily thread safe, so a refcount increase is not necessarily thread-safe.

    Update: Fixed unintentional misquote, used clearer wording

      x = x + 1, which you've already said isn't safe

      I never said that. I never implied that. For a start, what is "x"? It's not a perl variable is it. So it's just a meaningless equation.

      Do I need to demonstrate further,

      Yes. You need to demonstrate an actual segfault.

      Why. Because what you are suggesting is possible, is IMPOSSIBLE. IT CANNOT HAPPEN.

      Which makes your unfounded speculation: FUD. And, given that it is coming from you, a usually reliable and knowledgeable source, makes it dangerous and significant FUD. Possibly even deliberately malicious FUD.

      So please, demonstrate your good intent by either:

      1. demonstrating a segfault using one of your original three perl statements.
      2. withdrawing the FUD.

      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.

        I never said that. I never implied that

        Sorry, you said ||=, not increment. I had fixed it, but too slow it seems.

        For a start, what is "x"?

        I clearly said it was the ref count.

        You need to demonstrate an actual segfault.

        Why are you playing dumb? I wasted enough time with one. You can do the others yourself.

        Which makes your unfounded speculation: FUD

        It's not unfounded. I really don't know it to be thread-safe. It's not documented anywhere, and I don't have any reason to believe it is thread safe. Even you haven't said it was.

Log In?
Username:
Password:

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://867139]
help
Chatterbox?
and all is quiet...

How do I use this? | Other CB clients
Other Users?
Others about the Monastery: (6)
As of 2017-12-15 01:03 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?
    What programming language do you hate the most?




















    Results (415 votes). Check out past polls.

    Notices?