Subj : Re: Non-strictly-conforming and unspecified versus undefined behavior
To   : comp.programming.threads,comp.std.c
From : Gianni Mariani
Date : Tue Feb 22 2005 07:10 am

Alexander Terekhov wrote:
> Gianni Mariani wrote:
> [...]
> 
>>                                                              There are
>>definite merits to having objects accessible by only a single thread.
> 
> 
> Such as? 

a) It can be alot faster on some platforms.
b) Guarenteed that memory is private to a thread, reduces debugging issues.

> 
> 
>>What practical use is there in supporting only "thread specific" object
>>mappings ?
> 
> 
> Sharing. If you don't want sharing, use multiple processes, not 
> multiple threads within a process. 

Processes are far too restrictive.  The difference between a thread and 
a process is that a process does not share any memory (other than copy 
on modify).  What I want is that the threads share everything except 
when I specify otherwise.

I don't think you got it.

I want the ability to specify that an object is private to a thread, not 
ALL objects private to a thread.

Please indicate where this causes a problem for you.  I suspect I can 
show you a way to implement your desired functionality using the thread 
private mechanisms.

.