From: Anders Karlsson <anders@trudheim.com>
To: LKML <linux-kernel@vger.kernel.org>
Subject: comparision between signed and unsigned
Date: 04 May 2003 10:32:13 +0100 [thread overview]
Message-ID: <1052040732.25950.4.camel@marx> (raw)
[-- Attachment #1: Type: text/plain, Size: 430 bytes --]
Hi list,
Sitting here watching the compile output from 2.4.21-rc1-ac4 and
noticing there is a _lot_ of warnings about comparisions between signed
and unsigned values. The question I have is the following. If all the
signed values were modified to unsigned to fix the warnings, how likely
are things to break? Is there any reason to use signed values unless a
specific reason when negative values are required?
/Anders
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next reply other threads:[~2003-05-04 9:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-04 9:32 Anders Karlsson [this message]
2003-05-04 10:15 ` comparison between signed and unsigned Riley Williams
2003-05-04 13:15 ` Anders Karlsson
2003-05-04 16:10 ` comparision " Alan Cox
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=1052040732.25950.4.camel@marx \
--to=anders@trudheim.com \
--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