diff options
author | Paul Wilkinson <paul.wilkinson@cantab.net> | 2016-02-21 15:52:09 (GMT) |
---|---|---|
committer | Paul Wilkinson <paul.wilkinson@cantab.net> | 2016-02-21 15:52:09 (GMT) |
commit | 83d3b47acf8ab7ca010cacd9bc9f06bcabe69c38 (patch) | |
tree | 7cd07122db9c110006ffb17db02041ff84d5b699 /googletest/README.md | |
parent | 77d6b173380332b1c1bc540532641f410ec82d65 (diff) | |
download | googletest-83d3b47acf8ab7ca010cacd9bc9f06bcabe69c38.zip googletest-83d3b47acf8ab7ca010cacd9bc9f06bcabe69c38.tar.gz googletest-83d3b47acf8ab7ca010cacd9bc9f06bcabe69c38.tar.bz2 |
Fix formatting in AdvancedGuide.mdrefs/pull/719/head
Put occurrences of "#include" in a code span so they are not interpreted
as headers.
Other documents were not broken because the #include was not at the
start of the line, but put them in code spans anyway just in case the
text gets refilled in the future.
Diffstat (limited to 'googletest/README.md')
-rw-r--r-- | googletest/README.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/googletest/README.md b/googletest/README.md index e0ea1b0..edd4408 100644 --- a/googletest/README.md +++ b/googletest/README.md @@ -221,7 +221,7 @@ your build script. ### Avoiding Macro Name Clashes ### In C++, macros don't obey namespaces. Therefore two libraries that -both define a macro of the same name will clash if you #include both +both define a macro of the same name will clash if you `#include` both definitions. In case a Google Test macro clashes with another library, you can force Google Test to rename its macro to avoid the conflict. |