]> git.ipfire.org Git - thirdparty/gcc.git/commit
projects / thirdparty / gcc.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 338d687) | patch
doc/cpp: Document __has_include_next
authorArsen Arsenović <arsen@aarsen.me>
Fri, 18 Oct 2024 21:14:58 +0000 (23:14 +0200)
committerArsen Arsenović <arsen@gcc.gnu.org>
Thu, 21 Nov 2024 22:48:49 +0000 (23:48 +0100)
commitffeee625c53d882171af436222a7b18ed9ed89e1
tree2c26a975adb38c4e80a8cc8e5d77c7cf5beee66dtree
parent338d687e2a32f4e152d26c02319db1cb00401c3fcommit | diff
doc/cpp: Document __has_include_next

While hacking on an unrelated change, I noticed that __has_include_next
hasn't been documented at all.  This patch adds it to the __has_include
manual node.

gcc/ChangeLog:

* doc/cpp.texi (__has_include): Document __has_include_next
also.
(Conditional Syntax): Mention __has_include_next in the
description for the __has_include menu entry.
gcc/doc/cpp.texi diff | blob | blame | history
Mirror of https://gcc.gnu.org/git/gcc.git