summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorPaul Eggert <eggert@cs.ucla.edu>2023-02-09 17:09:23 -0800
committerPaul Eggert <eggert@cs.ucla.edu>2023-02-09 17:10:04 -0800
commit36f06b07d9cfb3974c160ecc22def3cb1b117106 (patch)
treeeba82ebe3f3873938c6183075ec26758fb7bf180 /doc
parent8eb1529674c157efe5ed902d361c8c779116d4a1 (diff)
downloadgnulib-36f06b07d9cfb3974c160ecc22def3cb1b117106.tar.gz
nullptr: work around Apple clang 14 issue
Problem reported by Bruno Haible in: https://lists.gnu.org/r/bug-gnulib/2023-02/msg00098.html * doc/gnulib.texi (nullptr): Document limitations better. * m4/nullptr.m4 (gl_NULLPTR): Check for incompatibility of macOS clang 14.0.0 (clang-1400.0.29.202), where <stddef.h> defines a non-working nullptr macro.
Diffstat (limited to 'doc')
-rw-r--r--doc/gnulib.texi7
1 files changed, 4 insertions, 3 deletions
diff --git a/doc/gnulib.texi b/doc/gnulib.texi
index 6fe2678834..28d8c20d8c 100644
--- a/doc/gnulib.texi
+++ b/doc/gnulib.texi
@@ -954,9 +954,10 @@ In C, it has type @code{void *}; in C++ it has an integer type.
@item
On older platforms Gnulib cannot easily emulate @code{nullptr_t}, so
-null pointer type checking is more error prone, and @code{_Generic}
-expressions cannot reliably distinguish @code{nullptr}'s type from
-integer or @code{void *} types.
+null pointer type checking is more error prone. In C, @code{_Generic}
+expressions cannot reliably distinguish the type of @code{nullptr}
+from integer or @code{void *} types. C++ overloading has similar
+limitations.
@end itemize
@node static_assert