Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!uwvax!puff!plocher
From: plocher@puff.wisc.edu (John Plocher)
Newsgroups: net.lang.c,net.micro.pc
Subject: Re: Signed char - What Foolishness Is This!
Message-ID: <246@puff.wisc.edu>
Date: Sat, 18-Oct-86 18:21:43 EDT
Article-I.D.: puff.246
Posted: Sat Oct 18 18:21:43 1986
Date-Received: Sat, 18-Oct-86 23:22:33 EDT
References: <8719@duke.duke.UUCP> <8273@sun.uucp>
Reply-To: plocher@puff.WISC.EDU (John Plocher)
Organization: U of Wisconsin CS Dept
Lines: 17
Keywords: RTFM :-)
Summary: did you try isascii() before doing isupper()?
Xref: mnetor net.lang.c:6140 net.micro.pc:7067

guy@sun.UUCP respondes to another poster about ctype macros
and characters on the IBM PC with the 8th bit set:
>> 1)      Do other C compilers make 'char' a signed quantity by default?
>
>I presume, by the way, that "isupper(<u-umlaut>)" is intended to return 0
>and "isupper(<U-umlaut>)" is intended to return 1.  If Microsoft didn't put
>the extended character set into the "ctype" tables, the way that the
>indexing is done is irrelevant.

  I hope you both remember that isANYTHING(x) is only defined to work
if isascii(x) is true!  isascii(u-umlaut) is FALSE!  Thus, isupper(u-umlaut)
does not NEED to work.
-- 
		harvard-\         /- uwmacc!uwhsms!plocher        (work)
John Plocher     seismo-->!uwvax!<
		  topaz-/         \- puff!plocher                 (school)
"Never trust an idea you get sitting down" - Nietzche