Re: Share .cpp and .h along projects

#5 at least is a sign of code with real bugs in it.

Oh, please. As I mentioned, being able to suppress interprocedural
optimization is a necessity for implementing mutex lock/unlock operations,

You use the volatile keyword for that, then you are robust against future
improvements in the optimizer.

and it also eliminates one of the problems in the DCLP. By putting
WaitForSingleObject, ReleaseMutex, and others in opaque system DLLs,
correct compiler behavior for MT programming WRT these operations
essentially comes for free.

Again, you use the volatile keyword for variables that are volatile. Trying
to get volatile behavior by changing to DLLs is bad.


.