From: Aaron Ballman Date: Wed, 16 Jan 2013 19:51:19 +0000 (+0000) Subject: Adding verbiage to the Language Extensions document about __has_include and __has_inc... X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=f5a45ea642b826a2312aa604a2e3fbf5269fc077;p=clang 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 --- 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: