From: terra@gnome.org (Morten Welinder)
To: pkoning@equallogic.com
Cc: gcc@gcc.gnu.org, dk@artimi.com
Subject: Re: signed vs unsigned pointer warning
Date: Wed, 22 Sep 2004 17:27:00 -0000 [thread overview]
Message-ID: <20040922164328.51BD61422D53@darter.rentec.com> (raw)
In-Reply-To: <16721.43357.693576.988329@gargle.gargle.HOWL> (message from Paul Koning on Wed, 22 Sep 2004 12:33:33 -0400)
> EOF isn't a character.
No-one said it was. It evaluates to an int.
> I don't understand your point. isprint takes a char * argument.
NO!
It takes an int argument. And only certain ints are valid: EOF
(== -1 everywhere, it seems) and the range of unsigned char, i.e.,
0-255. If you wanted to make signed args valid arguments -- and
doing so would be an extension to the standards -- then isprint
would need to be able to distinguish EOF and (int)(signed char)-1.
How do you propose to do that?
> You can do it by casts, by configure, or by using a 384 entry
> array, to mention just a few.
As it follows from the above, neither of these methods actually
work.
Morten
next prev parent reply other threads:[~2004-09-22 16:43 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-22 16:43 Morten Welinder
2004-09-22 17:17 ` Paul Koning
2004-09-22 17:27 ` Morten Welinder [this message]
2004-09-22 17:49 ` Dave Korn
2004-09-22 17:20 ` Dave Korn
2004-09-23 1:31 ` Andreas Schwab
2004-09-23 12:29 ` Dave Korn
2004-09-23 18:57 ` Joe Buck
2004-09-23 19:38 ` Dave Korn
2004-09-27 2:04 ` Jamie Lokier
2004-10-08 13:29 ` Nick Ing-Simmons
2004-10-08 13:32 ` Dave Korn
2004-10-08 17:20 ` Joe Buck
2004-10-08 17:28 ` Paul Jarc
2004-10-08 17:59 ` Joe Buck
2004-10-08 18:15 ` Dave Korn
2004-10-08 18:22 ` Joe Buck
2004-10-08 18:24 ` Jamie Lokier
2004-10-08 19:57 ` Paul Jarc
2004-10-09 7:05 ` Jamie Lokier
2004-10-09 8:48 ` Paul Jarc
2004-10-11 16:34 ` Richard Earnshaw
2004-10-08 18:57 ` Morten Welinder
2004-10-08 20:59 ` Matthias B.
2004-10-08 22:34 ` Paul Koning
2004-10-10 2:03 ` Matthias B.
2004-10-09 1:39 ` Andreas Schwab
2004-10-11 0:11 ` Kai Henningsen
-- strict thread matches above, loose matches on Subject: below --
2004-09-21 20:52 Richard Henderson
2004-09-21 22:36 ` Linus Torvalds
2004-09-22 14:35 ` Dave Korn
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=20040922164328.51BD61422D53@darter.rentec.com \
--to=terra@gnome.org \
--cc=dk@artimi.com \
--cc=gcc@gcc.gnu.org \
--cc=pkoning@equallogic.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).