Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!seismo!lll-lcc!rutgers!mit-eddie!husc6!necntc!encore!linus!philabs!micomvax!musocs!mcgill-vision!mouse From: mouse@mcgill-vision.UUCP (der Mouse) Newsgroups: comp.lang.c Subject: Re: draft ANSI standard: are chars signed? Message-ID: <590@mcgill-vision.UUCP> Date: Sun, 21-Dec-86 03:41:19 EST Article-I.D.: mcgill-v.590 Posted: Sun Dec 21 03:41:19 1986 Date-Received: Mon, 22-Dec-86 18:42:32 EST References: <1382@hoptoad.uucp> <8322@lll-crg.ARpA> <783@nscpdc.NSC.COM> <475@l.cc.purdue.edu> Organization: McGill University, Montreal Lines: 14 In article <475@l.cc.purdue.edu>, roz@l.cc.purdue.edu (Vu Qui Hao-Nhien) writes: > Of course, unless I'm wrong, they're not breaking ANY code, since all > they did was adding two more types -- signed char and unsigned char --, > not changing any current type. So apparently *no* code is broken. Is there a compiler left that barfs on unsigned char? I think (at least in practice) they really added only one type: signed char. der Mouse USA: {ihnp4,decvax,akgua,utzoo,etc}!utcsri!mcgill-vision!mouse think!mosart!mcgill-vision!mouse Europe: mcvax!decvax!utcsri!mcgill-vision!mouse ARPAnet: think!mosart!mcgill-vision!mouse@harvard.harvard.edu