This is the mail archive of the
mailing list for the GCC project.
RE: signed vs unsigned pointer warning
- From: "Dave Korn" <dk at artimi dot com>
- To: <gcc at gcc dot gnu dot org>
- Date: Wed, 22 Sep 2004 18:17:20 +0100
- Subject: RE: signed vs unsigned pointer warning
> -----Original Message-----
> From: Morten Welinder
> Sent: 22 September 2004 17:43
> > 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.
> It takes an int argument. And only certain ints are valid: EOF
> (== -1 everywhere, it seems) and the range of unsigned char, i.e.,
Heh. Can we not just work around this problem by replacing the definition
#define EOF -1U
[Ok, now I'm just being silly!]
Can't think of a witty .sigline today....