From ec25eea8f8237cf86c30703f59747e42f34b6f75 Mon Sep 17 00:00:00 2001 From: Abseil Team Date: Wed, 18 Jan 2023 09:43:14 -0800 Subject: [PATCH] Mention using MockFunction as a way to mock free functions. PiperOrigin-RevId: 502901538 Change-Id: I0cf351b9ad1411ae9c45e09550c24e006a24e179 --- docs/gmock_cook_book.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/docs/gmock_cook_book.md b/docs/gmock_cook_book.md index fc7db35b..d11282fa 100644 --- a/docs/gmock_cook_book.md +++ b/docs/gmock_cook_book.md @@ -285,6 +285,10 @@ If you are concerned about the performance overhead incurred by virtual functions, and profiling confirms your concern, you can combine this with the recipe for [mocking non-virtual methods](#MockingNonVirtualMethods). +Alternatively, instead of introducing a new interface, you can rewrite your code +to accept a std::function instead of the free function, and then use +[MockFunction](#MockFunction) to mock the std::function. + ### Old-Style `MOCK_METHODn` Macros Before the generic `MOCK_METHOD` macro