Shared Hell
    Kagamin 
    spam at here.lot
       
    Thu Oct 29 02:12:44 PDT 2009
    
    
  
Christopher Wright Wrote:
> > A function that accesses shared data has to put in fences. There's no 
> > way to have the same code deal with shared and unshared code.
> 
> Acquiring a lock on a non-shared instance is safe, just an unnecessary 
> expense. I would have looked into optimizing this expense away rather 
> than punting the problem to the programmer.
Shared code can put data into *really* shared environment, which must not happen for unshared data.
    
    
More information about the Digitalmars-d
mailing list