Re: New essay: The Best Synchronization is No Synchronization
- From: Joseph M. Newcomer <newcomer@xxxxxxxxxxxx>
- Date: Wed, 06 Jun 2007 09:14:52 -0400
It's fixed. Also added a sentence on montonic mutability, another interesting property
that the example I chose exhibits.
joe
On Wed, 06 Jun 2007 09:02:30 GMT, MrAsm <mrasm@xxxxxxx> wrote:
On Wed, 06 Jun 2007 01:52:14 -0400, Joseph M. NewcomerJoseph M. Newcomer [MVP]
<newcomer@xxxxxxxxxxxx> wrote:
http://www.flounder.com/no_synchronization.htm
Thank you.
I'm reading it.
However, I think there is a typo here:
<cite>
So in this case, if you anticipate subclasses will be created, you
would create protected methods to access the data, but declare the
actual variables PROTECTED so they cannot be accessed by any subclass.
</cite>
I think that PROTECTED in your text should be PRIVATE (because
'protected' variables can be accessed by derived classes).
MrAsm
email: newcomer@xxxxxxxxxxxx
Web: http://www.flounder.com
MVP Tips: http://www.flounder.com/mvp_tips.htm
.
- References:
- New essay: The Best Synchronization is No Synchronization
- From: Joseph M . Newcomer
- Re: New essay: The Best Synchronization is No Synchronization
- From: MrAsm
- New essay: The Best Synchronization is No Synchronization
- Prev by Date: Re: New essay: The Best Synchronization is No Synchronization
- Next by Date: Re: OninitDialog called once in a property page
- Previous by thread: Re: New essay: The Best Synchronization is No Synchronization
- Next by thread: Re: New essay: The Best Synchronization is No Synchronization
- Index(es):