* doc/gnulib-readme.texi (C language versions): Don’t be overly
specific about <sys/types.h>’s absence from the C standard.
---
 ChangeLog              | 6 ++++++
 doc/gnulib-readme.texi | 4 ++--
 2 files changed, 8 insertions(+), 2 deletions(-)

diff --git a/ChangeLog b/ChangeLog
index 1d543ca251..9201011285 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,9 @@
+2025-02-14  Paul Eggert  <egg...@cs.ucla.edu>
+
+       doc: “C11” → “C standard” for <sys/types.h>
+       * doc/gnulib-readme.texi (C language versions): Don’t be overly
+       specific about <sys/types.h>’s absence from the C standard.
+
 2025-02-14  Bruno Haible  <br...@clisp.org>
 
        isalnum_l: Fix errors in C++ mode.
diff --git a/doc/gnulib-readme.texi b/doc/gnulib-readme.texi
index 737134edcd..3d2d09fefb 100644
--- a/doc/gnulib-readme.texi
+++ b/doc/gnulib-readme.texi
@@ -331,8 +331,8 @@ list but is obsolescent as of C23.  Gnulib code can also 
assume the existence
 of @code{<ctype.h>}, @code{<errno.h>}, @code{<fcntl.h>},
 @code{<locale.h>}, @code{<signal.h>}, @code{<stdio.h>},
 @code{<stdlib.h>}, @code{<string.h>}, and @code{<time.h>}.  Similarly,
-many modules include @code{<sys/types.h>} even though it's not even in
-C11; that's OK since @code{<sys/types.h>} has been around nearly
+many modules include @code{<sys/types.h>} even though it's not
+in the C standard; that's OK since @code{<sys/types.h>} has been around nearly
 forever.
 
 Even if the include files exist, they may not conform to the C standard.
-- 
2.45.2


Reply via email to