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

See Tye's buried node

No point in even looking. It'll just be more uniformed, unfounded FUD based on nothing more than supposition and rumour.

Yup! Just as I suspected.

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^5: Utter FUD!
by Anonymous Monk on Oct 25, 2010 at 16:18 UTC

    So, agreeing with you in principle is FUD.

    Duly Noted.

[reply]

      The third and fourth & fifth sentences: a) are hardly tacit agreement; b) show a profound misunderstanding about the way threads works.

      There are no "copies" of shared variables, only aliases to them.

      Threads do not emulate fork (*). There is no attempt to have the spawned thread continue from the fork point of the parent.

      (*)Though they can be used to do so.

      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]

        Err, you are using alias there in a completely different sense than it is usually used in perl, and I think most people who know the details of how perl magic works would call it a copy, not an alias.

        In the sense tye was talking about, which has nothing to do with where a thread starts running, threads emulate fork (and not vfork, either).

        --
        A math joke: r = | |csc(θ)|+|sec(θ)|-||csc(θ)|-|sec(θ)|| |
        Online Fortune Cookie Search
        Office Space merchandise
[reply]

In Section Seekers of Perl Wisdom