summaryrefslogtreecommitdiffstats
path: root/googlemock
diff options
context:
space:
mode:
authorKrystian Kuzniarek <krystian.kuzniarek@gmail.com>2019-11-02 00:08:24 (GMT)
committerKrystian Kuzniarek <krystian.kuzniarek@gmail.com>2019-11-02 00:08:24 (GMT)
commit523ad489efc3a73dfbfdd5424c6ba518a3668593 (patch)
tree16482e37752640e73481ed08a7a208d167c011d4 /googlemock
parente8a82dc7ede61c4af3b9d75aa0e953b8cecfc8bb (diff)
downloadgoogletest-523ad489efc3a73dfbfdd5424c6ba518a3668593.zip
googletest-523ad489efc3a73dfbfdd5424c6ba518a3668593.tar.gz
googletest-523ad489efc3a73dfbfdd5424c6ba518a3668593.tar.bz2
update pump_manual.mdrefs/pull/2548/head
Diffstat (limited to 'googlemock')
-rw-r--r--googlemock/docs/pump_manual.md21
1 files changed, 9 insertions, 12 deletions
diff --git a/googlemock/docs/pump_manual.md b/googlemock/docs/pump_manual.md
index 10b3c5f..60ff06c 100644
--- a/googlemock/docs/pump_manual.md
+++ b/googlemock/docs/pump_manual.md
@@ -6,18 +6,15 @@ Template and macro libraries often need to define many classes, functions, or
macros that vary only (or almost only) in the number of arguments they take.
It's a lot of repetitive, mechanical, and error-prone work.
-Variadic templates and variadic macros can alleviate the problem. However, while
-both are being considered by the C++ committee, neither is in the standard yet
-or widely supported by compilers. Thus they are often not a good choice,
-especially when your code needs to be portable. And their capabilities are still
-limited.
-
-As a result, authors of such libraries often have to write scripts to generate
-their implementation. However, our experience is that it's tedious to write such
-scripts, which tend to reflect the structure of the generated code poorly and
-are often hard to read and edit. For example, a small change needed in the
-generated code may require some non-intuitive, non-trivial changes in the
-script. This is especially painful when experimenting with the code.
+Our experience is that it's tedious to write custom scripts, which tend to
+reflect the structure of the generated code poorly and are often hard to
+read and edit. For example, a small change needed in the generated code
+may require some non-intuitive, non-trivial changes in the script. This is
+especially painful when experimenting with the code.
+
+This script may be useful for generating meta code, for example a series of
+macros of FOO1, FOO2, etc. Nevertheless, please make it your last resort
+technique by favouring C++ template metaprogramming or variadic macros.
# Our Solution