Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!seismo!lll-crg!hoptoad!gnu From: gnu@hoptoad.uucp (John Gilmore) Newsgroups: comp.lang.c Subject: Re: draft ANSI standard: are chars signed? Message-ID: <1523@hoptoad.uucp> Date: Fri, 19-Dec-86 04:41:58 EST Article-I.D.: hoptoad.1523 Posted: Fri Dec 19 04:41:58 1986 Date-Received: Fri, 19-Dec-86 22:56:35 EST References: <1382@hoptoad.uucp> <8322@lll-crg.ARpA> <783@nscpdc.NSC.COM> <793@nscpdc.NSC.COM> Organization: Nebula Consultants in San Francisco Lines: 13 Four or ten people have taken me to task for saying that having "char" be either signed or unsigned has "broken code". They are right, it doesn't break any code. It just continues to make all such code nonportable, which is the current state of such code. Joe Mueller also points out that the proper way to make such code portable is to add "signed" and "unsigned" declarations such that you never declare anything "char" where it matters. Mea Culpa... -- John Gilmore {sun,ptsfa,lll-crg,ihnp4}!hoptoad!gnu jgilmore@lll-crg.arpa Call +1 800 854 7179 or +1 714 540 9870 and order X3.159-198x (ANSI C) for $65. Then spend two weeks reading it and weeping. THEN send in formal comments!