From: Paul Eggert Date: Thu, 9 Nov 2023 02:19:08 +0000 (-0800) Subject: Fix type typo in “String/Array Conventions” doc X-Git-Tag: glibc-2.39~298 X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=d1dcb565a1fb5829f9476a1438c30eccc4027d04;p=thirdparty%2Fglibc.git Fix type typo in “String/Array Conventions” doc * manual/string.texi (String/Array Conventions): Fix typo reported by Alejandro Colomar in: https://sourceware.org/pipermail/libc-alpha/2023-November/152646.html --- diff --git a/manual/string.texi b/manual/string.texi index 4149d54ee7f..6853e6655ac 100644 --- a/manual/string.texi +++ b/manual/string.texi @@ -178,7 +178,7 @@ beginning with @samp{mem} and @samp{wmem} (such as @code{memcpy} and @code{wmemcpy}) and invariably take an argument which specifies the size (in bytes and wide characters respectively) of the block of memory to operate on. The array arguments and return values for these functions -have type @code{void *} or @code{wchar_t}. As a matter of style, the +have type @code{void *} or @code{wchar_t *}. As a matter of style, the elements of the arrays used with the @samp{mem} functions are referred to as ``bytes''. You can pass any kind of pointer to these functions, and the @code{sizeof} operator is useful in computing the value for the