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

Clarifying language

Browse Source 
The old language might mislead someone into thinking that the access level on the base class itself was changed.
This commit is contained in:
Marzo Sette Torres Junior 2016-09-02 14:39:48 -03:00 committed by GitHub
parent ed9d1e1ff9
commit f700442db3
1 changed files with 3 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
googlemock/docs/CookBook.md
View File

@ -18,8 +18,9 @@ You must always put a mock method definition (`MOCK_METHOD*`) in a
`public:` section of the mock class, regardless of the method being `public:` section of the mock class, regardless of the method being
mocked being `public`, `protected`, or `private` in the base class. mocked being `public`, `protected`, or `private` in the base class.
This allows `ON_CALL` and `EXPECT_CALL` to reference the mock function This allows `ON_CALL` and `EXPECT_CALL` to reference the mock function
from outside of the mock class. (Yes, C++ allows a subclass to change from outside of the mock class. (Yes, C++ allows a subclass to specify
the access level of a virtual function in the base class.) Example: a different access level than the base class on a virtual function.)
Example:
``` ```
class Foo { class Foo {