Re: Why __memrchr vs. memrchr ?

[Denis Zaitsev <zzz@anda.ru>]

On Tue, Feb 03, 2004 at 07:03:40AM +0100, Andreas Jaeger wrote:
> Denis Zaitsev <zzz@anda.ru> writes:
> 
> > On Tue, Feb 03, 2004 at 01:17:23AM +0300, Dmitry V. Levin wrote:
> >> 
> >> According to memchr(3),
> >> "The memrchr() function is a GNU extension, available since glibc 2.1.91".
> >
> > Oh, I'm sorry.  This fact is omited from the texinfo GLIBC
> > documentation...
> 
> It's in the Library Summary:
> `void * memrchr (const void *BLOCK, int C, size_t SIZE)'
>      `string.h' (GNU):  *Note Search Functions::.

Indeed, it's shortly marked as (GNU) here and there.  But that's not
described in the texi manual.  So, below is the tiny patch.  Please,
apply it.


--- manual/string.texi.orig	2004-02-06 05:02:13.000000000 +0500
+++ manual/string.texi	2004-02-06 05:03:47.000000000 +0500
@@ -1625,6 +1625,8 @@ This function is a GNU extension.
 The function @code{memrchr} is like @code{memchr}, except that it searches
 backwards from the end of the block defined by @var{block} and @var{size}
 (instead of forwards from the front).
+
+This function is a GNU extension.
 @end deftypefun
 
 @comment string.h