From: Eric Blake <eblake@redhat.com>
To: Richard Henderson <rth@twiddle.net>
Cc: Martin Husemann <martin@duskware.de>,
Laszlo Ersek <lersek@redhat.com>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Git head build problem (popcountl vs. system headers)
Date: Thu, 25 Apr 2013 11:39:05 -0600 [thread overview]
Message-ID: <51796A39.3020003@redhat.com> (raw)
In-Reply-To: <51796350.9080306@twiddle.net>
[-- Attachment #1: Type: text/plain, Size: 1057 bytes --]
On 04/25/2013 11:09 AM, Richard Henderson wrote:
> On 2013-04-25 14:38, Laszlo Ersek wrote:
>>> <strings.h> is the K&R header supplanted by ISO <string.h>.
>>> Is there any good reason that we're including it at all?
>>
>> - <strings.h> is a portable SUS/POSIX header:
>>
>> http://pubs.opengroup.org/onlinepubs/9699919799/basedefs/strings.h.html
>
> Huh. Ok, fine, but what do we think we're using out of it that
> isn't in <string.h>?
strcasecmp(). Just because some (many) systems pollute <string.h> with
strcasecmp() without you having to explicitly include <strings.h> (and
POSIX allows but not requires this:
http://pubs.opengroup.org/onlinepubs/9699919799/functions/V2_chap02.html#tag_15_02_02
says that the str* prefix is reserved in <string.h>), a
strictly-conforming implementation cannot rely on this extension, and
there are systems where you have to get strcasecmp() from <strings.h>,
just as POSIX requires.
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 621 bytes --]
next prev parent reply other threads:[~2013-04-25 17:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-25 6:47 [Qemu-devel] Git head build problem (popcountl vs. system headers) Martin Husemann
2013-04-25 10:36 ` Richard Henderson
2013-04-25 13:38 ` Laszlo Ersek
2013-04-25 17:09 ` Richard Henderson
2013-04-25 17:39 ` Eric Blake [this message]
2013-04-25 18:36 ` Martin Husemann
2013-04-25 18:48 ` Peter Maydell
2013-04-27 18:50 ` Martin Husemann
2013-05-05 12:29 ` Blue Swirl
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=51796A39.3020003@redhat.com \
--to=eblake@redhat.com \
--cc=lersek@redhat.com \
--cc=martin@duskware.de \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
/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).