aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorAaron Ballman <aaron@aaronballman.com>2013-01-16 19:51:19 +0000
committerAaron Ballman <aaron@aaronballman.com>2013-01-16 19:51:19 +0000
commitf5a45ea642b826a2312aa604a2e3fbf5269fc077 (patch)
tree32cf5e1e735f950fac2fc4bfdbf87b3a46f44121
parent31672b1745195d709b641f1c0f44e203742fa73b (diff)
Adding verbiage to the Language Extensions document about __has_include and __has_include_next only being allowed within preprocessor directives.
git-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@172643 91177308-0d34-0410-b5e6-96231b3b80d8
-rw-r--r--docs/LanguageExtensions.rst3
1 files changed, 2 insertions, 1 deletions
diff --git a/docs/LanguageExtensions.rst b/docs/LanguageExtensions.rst
index be54402fd3..2abbea7da6 100644
--- a/docs/LanguageExtensions.rst
+++ b/docs/LanguageExtensions.rst
@@ -140,7 +140,8 @@ Include File Checking Macros
Not all developments systems have the same include files. The
:ref:`langext-__has_include` and :ref:`langext-__has_include_next` macros allow
you to check for the existence of an include file before doing a possibly
-failing ``#include`` directive.
+failing ``#include`` directive. Include file checking macros must be used
+as expressions in #if or #elif preprocessing directives.
.. _langext-__has_include: