From: Andreas Jaeger <aj@suse.de>
To: libc-alpha@sources.redhat.com
Cc: linux-gcc@vger.kernel.org
Subject: Re: Why __memrchr vs. memrchr ?
Date: Tue, 03 Feb 2004 07:03:40 +0100 [thread overview]
Message-ID: <m3ektcsnr7.fsf@gromit.moeb> (raw)
In-Reply-To: <20040203053002.A21975@zzz.ward.six> (Denis Zaitsev's message of "Tue, 3 Feb 2004 05:30:02 +0500")
[-- Attachment #1: Type: text/plain, Size: 979 bytes --]
Denis Zaitsev <zzz@anda.ru> writes:
> On Tue, Feb 03, 2004 at 01:17:23AM +0300, Dmitry V. Levin wrote:
>> Hi,
>>
>> On Tue, Feb 03, 2004 at 02:37:21AM +0500, Denis Zaitsev wrote:
>> > Why such a scheme is used in GLIBC:
>> >
>> > declare + define __memrchr, and than
>> >
>> > # ifdef __USE_GNU
>> > # define memrchr(s, c, n) __memrchr ((s), (c), (n))
>> > # endif
>> >
>> > ? memrchr is not the GNU extension, is it?
>>
>> 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::.
Andreas
--
Andreas Jaeger, aj@suse.de, http://www.suse.de/~aj
SuSE Linux AG, Maxfeldstr. 5, 90409 Nürnberg, Germany
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
[-- Attachment #2: Type: application/pgp-signature, Size: 188 bytes --]
next prev parent reply other threads:[~2004-02-03 6:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-02 21:37 Why __memrchr vs. memrchr ? Denis Zaitsev
2004-02-02 22:17 ` Dmitry V. Levin
2004-02-03 0:30 ` Denis Zaitsev
2004-02-03 6:03 ` Andreas Jaeger [this message]
2004-02-06 0:08 ` Denis Zaitsev
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3ektcsnr7.fsf@gromit.moeb \
--to=aj@suse.de \
--cc=libc-alpha@sources.redhat.com \
--cc=linux-gcc@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).