From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-return-103109-listarch-gcc=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 19997 invoked by alias); 22 Sep 2004 17:20:06 -0000
Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Archive: <http://gcc.gnu.org/ml/gcc/>
List-Post: <mailto:gcc@gcc.gnu.org>
List-Help: <http://gcc.gnu.org/ml/>
Sender: gcc-owner@gcc.gnu.org
Received: (qmail 19988 invoked from network); 22 Sep 2004 17:20:06 -0000
Received: from unknown (HELO NUTMEG.CAM.ARTIMI.COM) (217.40.111.177)
  by sourceware.org with SMTP; 22 Sep 2004 17:20:06 -0000
Received: from mace ([192.168.1.25]) by NUTMEG.CAM.ARTIMI.COM with Microsoft SMTPSVC(6.0.3790.0);
	 Wed, 22 Sep 2004 18:20:04 +0100
From: "Dave Korn" <dk@artimi.com>
To: <gcc@gcc.gnu.org>
Subject: RE: signed vs unsigned pointer warning
Date: Wed, 22 Sep 2004 17:49:00 -0000
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
In-Reply-To: <20040922164328.51BD61422D53@darter.rentec.com>
Message-ID: <NUTMEGNoEvlo0vxSGeC0000002a@NUTMEG.CAM.ARTIMI.COM>
X-OriginalArrivalTime: 22 Sep 2004 17:20:04.0908 (UTC) FILETIME=[66A306C0:01C4A0C8]
X-SW-Source: 2004-09/txt/msg01296.txt.bz2

> -----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.
> 
> 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.  

Heh.  Can we not just work around this problem by replacing the definition
of EOF

#define EOF -1U

;)

[Ok, now I'm just being silly!]

    cheers, 
      DaveK
-- 
Can't think of a witty .sigline today....