summaryrefslogtreecommitdiffstats
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
commit1f0fa91bedbefd02c9298ad52291313bf1099a0b (patch)
treea7f08f9a55746af2a172816cb8fa057aba47d336
parentda09857394818160c4e51c467cdb9c9b3d589e80 (diff)
downloadbcm5719-llvm-1f0fa91bedbefd02c9298ad52291313bf1099a0b.tar.gz
bcm5719-llvm-1f0fa91bedbefd02c9298ad52291313bf1099a0b.zip
Adding verbiage to the Language Extensions document about __has_include and __has_include_next only being allowed within preprocessor directives.
llvm-svn: 172643
-rw-r--r--clang/docs/LanguageExtensions.rst3
1 files changed, 2 insertions, 1 deletions
diff --git a/clang/docs/LanguageExtensions.rst b/clang/docs/LanguageExtensions.rst
index be54402fd3f..2abbea7da69 100644
--- a/clang/docs/LanguageExtensions.rst
+++ b/clang/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:
OpenPOWER on IntegriCloud