[PROPOSED 3/4] explicit_bzero: memset_explicit is standard

[Paul Eggert]

* doc/glibc-functions/explicit_bzero.texi:
Say that memset_explicit is preferred in new code.
---
 ChangeLog                               | 4 ++++
 doc/glibc-functions/explicit_bzero.texi | 4 ++++
 2 files changed, 8 insertions(+)

diff --git a/ChangeLog b/ChangeLog
index 2d29d1f646..ea76fef399 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,5 +1,9 @@
 2022-11-27  Paul Eggert  <eggert@cs.ucla.edu>
 
+       explicit_bzero: memset_explicit is standard
+       * doc/glibc-functions/explicit_bzero.texi:
+       Say that memset_explicit is preferred in new code.
+
        read-file: use memset_explicit
        * lib/read-file.c (fread_file, read_file):
        Use memset_explicit instead of explicit_bzero.
diff --git a/doc/glibc-functions/explicit_bzero.texi 
b/doc/glibc-functions/explicit_bzero.texi
index 31b4c9c011..a356659d27 100644
--- a/doc/glibc-functions/explicit_bzero.texi
+++ b/doc/glibc-functions/explicit_bzero.texi
@@ -24,6 +24,10 @@ question, the information that was in memory may still be 
available
 elsewhere on the machine.  Proper implementation of information
 erasure requires support from levels below C code.
 
+C23 specifies the function @code{memset_explicit}, which should be
+preferred to @code{explicit_bzero} in new code.
+@xref{memset_explicit}.
+
 Portability problems fixed by Gnulib:
 @itemize
 @item
-- 
2.37.2