Subj : Re: Lockable objects
To   : comp.programming.threads
From : Torsten Robitzki
Date : Thu May 19 2005 10:58 pm

>>What can a user do with a container that have a buildin mutex that the
>>user can not do with a container plus a mutex? What is the difference of:
>>mutex m; std::vector<int> v;
>>
>>to your approach and to something like std::pair<mutex, std::vector<int> > ?
> 
> 
> Many things could be automated, and more advanced things could be realized.
> Such argumentation like yours were also happening before templates in C++.
> Today they are very important.  Tomorrow threading and locking of objects will be.

I begin to wonder if you are a human beeing or just a agent of some AI 
project. I've ask a cristal clean question and got some "everything will 
by much easier" answer.

So again for the robots: 0100100100001111010010010?

Or in the more verbose form:
What is the difference between your silly approache and
std::pair<mutex, std::vector<what_ever> > ?


> 
>>>And: multithreading has become a de facto standard in programming,
>>>esp. in application programming.
>>
>>Really? Did your teacher told you that? Why especial for application
>>programming?
> 
> 
> Because the old school programmers have yet to (ie. won't) understand their power.
> It's only a matter of time.

So I might conclude: "Multithreading has become a de facto standard in 
application programming because the old school programmers have yet to 
understand their power". Am I'm right? Does this makes any sense to you?

.