Subj : Re: Can C++ local static objects be made thread safe? To : comp.programming.threads,comp.std.c From : David Hopwood Date : Thu Feb 17 2005 11:55 pm David Schwartz wrote: > "Alexander Terekhov" wrote in message > news:42131205.B72DB5C2@web.de... > >>Under C/POSIX different objects just can't have the same address. >>And threads share the entire address space. By definition. > > That's ridiculous. Providing no strictly-conforming code can tell the > difference, POSIX is silent. I keep hearing this idea that POSIX (or Standard C) only imposes requirements for strictly-conforming code. Where does it come from? Can you explain why you believe it? C99 4 #3 definitely (although not particularly clearly) says otherwise. ("A program that is correct in all other aspects, operating on correct data, containing unspecified behavior shall be a correct program and act in accordance with 5.1.2.3.") This is quite relevant to c.p.threads, BTW. Not imposing any requirements for code that has nondeterministic, i.e. unspecified, behaviour would make POSIX useless for multithreaded programming. -- David Hopwood .