From 765cbccf8687ebc285f9e5cb01b084f57bec7e9c Mon Sep 17 00:00:00 2001 From: "wan@google.com" Date: Mon, 19 Apr 2010 20:49:41 +0000 Subject: [PATCH] wiki change: updates the primer on gtest's thread safety. --- wiki/GoogleTestPrimer.wiki | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/wiki/GoogleTestPrimer.wiki b/wiki/GoogleTestPrimer.wiki index 321e7d7b..3e4c7306 100644 --- a/wiki/GoogleTestPrimer.wiki +++ b/wiki/GoogleTestPrimer.wiki @@ -488,10 +488,10 @@ GoogleTestAdvancedGuide, which describes many more useful Google Test features. = Known Limitations = -Google Test is designed to be thread-safe. However, we haven't had -time to implement the synchronization primitives on various platforms -yet. Therefore, it is currently _unsafe_ to use Google Test -assertions from two threads concurrently. In most tests this is not -an issue as usually the assertions are done in the main thread. If you -want to help, you can volunteer to implement the necessary -synchronization primitives in `gtest-port.h`. \ No newline at end of file +Google Test is designed to be thread-safe. The implementation is +thread-safe on systems where the `pthreads` library is available. It +is currently _unsafe_ to use Google Test assertions from two threads +concurrently on other systems (e.g. Windows). In most tests this is +not an issue as usually the assertions are done in the main thread. If +you want to help, you can volunteer to implement the necessary +synchronization primitives in `gtest-port.h` for your platform. \ No newline at end of file