eson/googletest
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Use gender-neutral pronouns in comments and docs

Browse Source
This commit is contained in:
Jonathan Wakely
2017-09-27 13:31:13 +01:00
parent cd8f5d1729
commit c61e22b1fe
20 changed files with 22 additions and 22 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
googletest/docs/AdvancedGuide.md
View File

@@ -1263,7 +1263,7 @@ known as <i>abstract tests</i>. As an example of its application, when you
are designing an interface you can write a standard suite of abstract
tests (perhaps using a factory function as the test parameter) that
all implementations of the interface are expected to pass. When
someone implements the interface, he can instantiate your suite to get
someone implements the interface, they can instantiate your suite to get
all the interface-conformance tests for free.
To define abstract tests, you should organize your code like this:

4
googletest/docs/FAQ.md
View File

@@ -102,9 +102,9 @@ Then every user of your machine can write tests without
recompiling Google Test.
This seemed like a good idea, but it has a
got-cha: every user needs to compile his tests using the _same_ compiler
got-cha: every user needs to compile their tests using the _same_ compiler
flags used to compile the installed Google Test libraries; otherwise
he may run into undefined behaviors (i.e. the tests can behave
they may run into undefined behaviors (i.e. the tests can behave
strangely and may even crash for no obvious reasons).
Why? Because C++ has this thing called the One-Definition Rule: if