Re^5: Why it is important to counter FUD.

If you are concieving of a tutorial as the "Unified Field Theory" of threading, you have a point. However, you have a great deal of accumulated knowledge spread out across many nodes and depths of reply. I think it would be helpful to many if you would gather than knowledge together and present it in a single read through document.

Call it "A field guide to some common threading problems" if you wish. Fill the introduction with a disclaimer about what the essay does not discuss. Include the essay above, if you think it would help. I think the benefit would be in having a one-stop shopping location for BrowserUK's insights and years of experience, not in having the final "perfect" and "correct" exposition of all threading issues known to human kind.

Comment on Re^5: Why it is important to counter FUD.

Replies are listed 'Best First'.
Re^6: Why it is important to counter FUD. by BrowserUk (Patriarch) on Jan 03, 2011 at 12:18 UTC
Oh dear. I guess my analogy was too big and too abstract. My point was simply that knowledge evolves. All perl programs are threaded; and starting a second or subsequent thread is trivial. The devil is in the ITC. Beyond simply listing the already well known mechanisms, there is generically, little more to be said beyond what is already in the documentation. Picking the right mechanism depends entirely upon the specific of each application. And any single application might conceivably require the use of all ITC mechanisms. Picking the "right" implementation for each piece of communication likewise. It doesn't make sense to use a queue to share the state of a single value. It doesn't make sense to use a shared scalar to share a stream of values. As for the one stop shop: This is as good a summary of those 3000 posts as I can come up with. 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]

Replies are listed 'Best First'.

Re^6: Why it is important to counter FUD.
by BrowserUk (Patriarch) on Jan 03, 2011 at 12:18 UTC

Oh dear. I guess my analogy was too big and too abstract. My point was simply that knowledge evolves.

All perl programs are threaded; and starting a second or subsequent thread is trivial. The devil is in the ITC.

Beyond simply listing the already well known mechanisms, there is generically, little more to be said beyond what is already in the documentation.

Picking the right mechanism depends entirely upon the specific of each application. And any single application might conceivably require the use of all ITC mechanisms. Picking the "right" implementation for each piece of communication likewise. It doesn't make sense to use a queue to share the state of a single value. It doesn't make sense to use a shared scalar to share a stream of values.

As for the one stop shop: This is as good a summary of those 3000 posts as I can come up with.

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]