Skip to content
Projects
Groups
Snippets
Help
This project
Loading...
Sign in / Register
Toggle navigation
G
googletest
Project
Overview
Details
Activity
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
0
Issues
0
List
Board
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Charts
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
Chen Yisong
googletest
Commits
20714749
Commit
20714749
authored
Mar 16, 2016
by
Manuel Binna
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Fix whitespace in paragraph
parent
72416fab
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
4 additions
and
5 deletions
+4
-5
AdvancedGuide.md
googletest/docs/AdvancedGuide.md
+4
-5
No files found.
googletest/docs/AdvancedGuide.md
View file @
20714749
...
...
@@ -1571,15 +1571,14 @@ For technical reasons, there are some caveats:
1.
_statement_ in
`EXPECT_FATAL_FAILURE()`
cannot reference local non-static variables or non-static members of
`this`
object.
1.
_statement_ in
`EXPECT_FATAL_FAILURE()`
cannot return a value.
_Note:_
Google Test is designed with threads in mind.
Once the
_Note:_
Google Test is designed with threads in mind. Once the
synchronization primitives in
`"gtest/internal/gtest-port.h"`
have
been implemented, Google Test will become thread-safe, meaning that
you can then use assertions in multiple threads concurrently. Before
that, however, Google Test only supports single-threaded usage. Once
you can then use assertions in multiple threads concurrently. Before
that, however, Google Test only supports single-threaded usage. Once
thread-safe,
`EXPECT_FATAL_FAILURE()`
and
`EXPECT_NONFATAL_FAILURE()`
will capture failures in the current thread only. If _statement_
creates new threads, failures in these threads will be ignored.
If
creates new threads, failures in these threads will be ignored. If
you want to capture failures from all threads instead, you should use
the following macros:
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment