From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Pierre Ossman <drzeus-list@drzeus.cx>
Cc: Bernd Petrovitsch <bernd@firmix.at>,
kbuild-devel@lists.sourceforge.net,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Pointer cast warnings in scripts/
Date: Wed, 22 Jun 2005 12:25:06 +0100 [thread overview]
Message-ID: <20050622122506.A5226@flint.arm.linux.org.uk> (raw)
In-Reply-To: <42B94786.2010403@drzeus.cx>; from drzeus-list@drzeus.cx on Wed, Jun 22, 2005 at 01:12:06PM +0200
On Wed, Jun 22, 2005 at 01:12:06PM +0200, Pierre Ossman wrote:
> That doesn't really make it a standard though (de facto perhaps). :)
> The odds of all those man pages deviating from the standard is probably
> very low. But unless someone has actually read the damn thing we won't
> know for sure.
You could check the C99 spec of course, which says gives (eg) strcmp as:
int strcmp(const char *s1, const char *s2);
rmk's rules of char:
1. use char for character strings and individual characters
2. use signed char if your data type relies upon negative char values
3. use unsigned char if your data type does not require negative char
values, especially if it makes use of the positive values not
present in the signed char range.
IOW, use signed/unsigned when you need to explicitly state your
requirements, but omit it for true strings and characters.
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of: 2.6 Serial core
next prev parent reply other threads:[~2005-06-22 11:25 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-21 11:17 [PATCH] Pointer cast warnings in scripts/ Pierre Ossman
2005-06-21 12:06 ` Mikael Pettersson
2005-06-21 12:18 ` Roman Zippel
2005-06-21 12:41 ` Pierre Ossman
2005-06-21 12:51 ` Roman Zippel
2005-06-21 12:59 ` Pierre Ossman
2005-06-21 13:14 ` Bernd Petrovitsch
2005-06-22 9:21 ` Pierre Ossman
2005-06-22 10:04 ` Bernd Petrovitsch
2005-06-22 11:12 ` Pierre Ossman
2005-06-22 11:25 ` Russell King [this message]
2005-06-21 13:20 ` Roman Zippel
2005-06-21 14:06 ` Pierre Ossman
2005-06-21 14:14 ` Roman Zippel
2005-06-21 21:31 ` J.A. Magallon
2005-06-21 14:19 ` J.A. Magallon
2005-06-21 13:25 ` Andreas Schwab
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=20050622122506.A5226@flint.arm.linux.org.uk \
--to=rmk+lkml@arm.linux.org.uk \
--cc=bernd@firmix.at \
--cc=drzeus-list@drzeus.cx \
--cc=kbuild-devel@lists.sourceforge.net \
--cc=linux-kernel@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