Re^12: is ||= threadsafe?

I said I didn't know that it was safe.

I don't know for sure that when Perl is run on *nix, it doesn't irradiate kittens in the third world, but I don't go around posting such non-information in response to every Perl on Linux question that arises here.

I never said or implied there was a bug.

If what you speculated was true--it would be a bug. A bug so common that it would obvious to anyone who spends as much time here as you do.

The fallacy is the idea that such obvious possibilities were not a fundamental part of the design from the outset.

So you knew it was thread safe, but decided to try to catch me in a non-existent lie instead saying so? wtf?

It was possible that you knew of an obscure bug that I have never heard of--it has happened several times before.

Hence my initially asking for further information. From there, (minus the bits you indelibly erased) ... is on the record.

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

Comment on Re^12: is \|\|= threadsafe?

Replies are listed 'Best First'.
Re^13: is \|\|= threadsafe? by ikegami (Patriarch) on Oct 25, 2010 at 17:08 UTC
I don't go around posting such non-information in response to every Perl on Linux question that arises here. Of course not. Like I've already explained, I was seeking information. If what you speculated was true--it would be a bug. How is locking shared variables before using them a bug? You have to do so in other languages.	[reply]