Skip to content
Snippets Groups Projects
Commit f5a45ea6 authored by Aaron Ballman's avatar Aaron Ballman
Browse files

Adding verbiage to the Language Extensions document about __has_include and...

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
parent 31672b17
No related branches found
No related tags found
No related merge requests found
...@@ -140,7 +140,8 @@ Include File Checking Macros ...@@ -140,7 +140,8 @@ Include File Checking Macros
Not all developments systems have the same include files. The Not all developments systems have the same include files. The
:ref:`langext-__has_include` and :ref:`langext-__has_include_next` macros allow :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 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: .. _langext-__has_include:
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment