aboutsummaryrefslogtreecommitdiffstats
path: root/include
diff options
context:
space:
mode:
authorzhanyong.wan <zhanyong.wan@8415998a-534a-0410-bf83-d39667b30386>2009-05-05 23:14:47 +0000
committerzhanyong.wan <zhanyong.wan@8415998a-534a-0410-bf83-d39667b30386>2009-05-05 23:14:47 +0000
commite7bb5ededa4df6ec430c1e84154bc01bf84d4ecc (patch)
tree26a95c5d0237def74e51c633877d5cfc308db19d /include
parent125783fb87488239c062422bece2a9302489aafd (diff)
downloadgoogletest-e7bb5ededa4df6ec430c1e84154bc01bf84d4ecc.tar.gz
googletest-e7bb5ededa4df6ec430c1e84154bc01bf84d4ecc.tar.bz2
googletest-e7bb5ededa4df6ec430c1e84154bc01bf84d4ecc.zip
Improves the error message for leaked mocks to include the test name (by Zhanyong Wan).
Diffstat (limited to 'include')
-rw-r--r--include/gmock/internal/gmock-port.h8
1 files changed, 4 insertions, 4 deletions
diff --git a/include/gmock/internal/gmock-port.h b/include/gmock/internal/gmock-port.h
index cad195ad..d242c8e4 100644
--- a/include/gmock/internal/gmock-port.h
+++ b/include/gmock/internal/gmock-port.h
@@ -166,16 +166,16 @@ inline To down_cast(From* f) { // so we only accept pointers
return static_cast<To>(f);
}
-// The GMOCK_COMPILE_ASSERT macro can be used to verify that a compile time
+// The GMOCK_COMPILE_ASSERT_ macro can be used to verify that a compile time
// expression is true. For example, you could use it to verify the
// size of a static array:
//
-// GMOCK_COMPILE_ASSERT(ARRAYSIZE(content_type_names) == CONTENT_NUM_TYPES,
-// content_type_names_incorrect_size);
+// GMOCK_COMPILE_ASSERT_(ARRAYSIZE(content_type_names) == CONTENT_NUM_TYPES,
+// content_type_names_incorrect_size);
//
// or to make sure a struct is smaller than a certain size:
//
-// GMOCK_COMPILE_ASSERT(sizeof(foo) < 128, foo_too_large);
+// GMOCK_COMPILE_ASSERT_(sizeof(foo) < 128, foo_too_large);
//
// The second argument to the macro is the name of the variable. If
// the expression is false, most compilers will issue a warning/error