diff options
| author | Jonathan Wakely <jwakely@redhat.com> | 2017-09-27 13:31:13 +0100 |
|---|---|---|
| committer | Jonathan Wakely <jwakely@redhat.com> | 2017-09-27 13:31:13 +0100 |
| commit | b70cf1a663ad30f77ab9867095a87d3d5429450d (patch) | |
| tree | ac98f22d19193c60ceecba1aca0c7d824d32f77f /googlemock/docs | |
| parent | f1a87d73fc604c5ab8fbb0cc6fa9a86ffd845530 (diff) | |
| download | googletest-b70cf1a663ad30f77ab9867095a87d3d5429450d.tar.gz googletest-b70cf1a663ad30f77ab9867095a87d3d5429450d.tar.bz2 googletest-b70cf1a663ad30f77ab9867095a87d3d5429450d.zip | |
Use gender-neutral pronouns in comments and docs
Diffstat (limited to 'googlemock/docs')
| -rw-r--r-- | googlemock/docs/CookBook.md | 2 | ||||
| -rw-r--r-- | googlemock/docs/FrequentlyAskedQuestions.md | 2 |
2 files changed, 2 insertions, 2 deletions
diff --git a/googlemock/docs/CookBook.md b/googlemock/docs/CookBook.md index 753c6dd3..3d07e68b 100644 --- a/googlemock/docs/CookBook.md +++ b/googlemock/docs/CookBook.md @@ -227,7 +227,7 @@ If a mock method has no `EXPECT_CALL` spec but is called, Google Mock will print a warning about the "uninteresting call". The rationale is: * New methods may be added to an interface after a test is written. We shouldn't fail a test just because a method it doesn't know about is called. - * However, this may also mean there's a bug in the test, so Google Mock shouldn't be silent either. If the user believes these calls are harmless, he can add an `EXPECT_CALL()` to suppress the warning. + * However, this may also mean there's a bug in the test, so Google Mock shouldn't be silent either. If the user believes these calls are harmless, they can add an `EXPECT_CALL()` to suppress the warning. However, sometimes you may want to suppress all "uninteresting call" warnings, while sometimes you may want the opposite, i.e. to treat all diff --git a/googlemock/docs/FrequentlyAskedQuestions.md b/googlemock/docs/FrequentlyAskedQuestions.md index 5eac83f4..ccaa3d7a 100644 --- a/googlemock/docs/FrequentlyAskedQuestions.md +++ b/googlemock/docs/FrequentlyAskedQuestions.md @@ -240,7 +240,7 @@ You cannot mock a variadic function (i.e. a function taking ellipsis The problem is that in general, there is _no way_ for a mock object to know how many arguments are passed to the variadic method, and what the arguments' types are. Only the _author of the base class_ knows -the protocol, and we cannot look into his head. +the protocol, and we cannot look into their head. Therefore, to mock such a function, the _user_ must teach the mock object how to figure out the number of arguments and their types. One |