Re: CSingleLock same-thread double-access problem.
- From: Joseph M. Newcomer <newcomer@xxxxxxxxxxxx>
- Date: Thu, 27 Sep 2007 20:31:29 -0400
I heard a lecture the other night on physicists of the 20th century, and Pauli, commenting
on a particularly bad paper, remarked that "the paper is so bad, it's not even wrong".
I seriously worry about the degradation in the quality of the documentation; the most
recent documentation is at the very best, poorly organized, badly-cross-referenced, and
incomplete. But the article you cited is a new low, rivaling the multithreaded networking
article I discovered (I realized a while ago that one of the complete and total disasters
one of my clients presented me with was based entirely on that article, although I didn't
realize it at the time. This article had cost them at least $100,000 in effort, and I
told them nothing short of a total rewrite was going to salvage the product, and they
couldn't afford that. The product was withdrawn. All due to some incompetent
documentation that had no oversight or review)
OTOH, I was trying to write a VBA extension to PowerPoint recently, and when it comes to
poor quality of documentation, only the Unix 'man' pages, that hold the honor of being the
World's Worst Documentation keep it from holding that honor. So I suppose we should be
grateful that we have what we have.
Nonetheless, the quality is definitely going down.
joe
On Thu, 27 Sep 2007 15:50:05 -0500, "Doug Harrison [MVP]" <dsh@xxxxxxxx> wrote:
On Thu, 27 Sep 2007 14:45:30 -0400, Joseph M. NewcomerJoseph M. Newcomer [MVP]
<newcomer@xxxxxxxxxxxx> wrote:
Good points all. Adding methods such as InterlockedAddToTail as an interlocked version of
AddToTail, for example, in a derived subclass of CList.
There is a persistent myth among some C++ programmers that NOTHING can be done without a
class to represent it, which I find odd.
joe
Thanks, I was going to end my message by suggesting he look up
_lock_file/_fgetc_nolock to further illustrate what I was talking about,
but after reading the _lock_file docs, I instead entered this bug report:
https://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=300428
Every sentence in this topic contains an error, and its example "works"
purely by accident. Usually, there is a germ of truth in most MSDN docs,
but this one deserves some sort of "Most Wrong" award.
email: newcomer@xxxxxxxxxxxx
Web: http://www.flounder.com
MVP Tips: http://www.flounder.com/mvp_tips.htm
.
- Follow-Ups:
- Re: CSingleLock same-thread double-access problem.
- From: Alexander Grigoriev
- Re: CSingleLock same-thread double-access problem.
- References:
- CSingleLock same-thread double-access problem.
- From: Ricardo Vazquez
- Re: CSingleLock same-thread double-access problem.
- From: Joseph M . Newcomer
- Re: CSingleLock same-thread double-access problem.
- From: Ricardo Vazquez
- Re: CSingleLock same-thread double-access problem.
- From: Doug Harrison [MVP]
- Re: CSingleLock same-thread double-access problem.
- From: Joseph M . Newcomer
- Re: CSingleLock same-thread double-access problem.
- From: Doug Harrison [MVP]
- CSingleLock same-thread double-access problem.
- Prev by Date: Re: Access violation in AFX_MAINTAIN_STATE2::AFX_MAINTAIN_STATE2
- Next by Date: Re: Access violation in AFX_MAINTAIN_STATE2::AFX_MAINTAIN_STATE2
- Previous by thread: Re: CSingleLock same-thread double-access problem.
- Next by thread: Re: CSingleLock same-thread double-access problem.
- Index(es):
Relevant Pages
|