Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!hplabs!hp-pcd!hplsla!jima
From: jima@hplsla.HP.COM (Jim Adcock)
Newsgroups: comp.lang.c++
Subject: Re: "Signed" Implemented Yet?
Message-ID: <6590250@hplsla.HP.COM>
Date: 12 Sep 89 17:18:00 GMT
References: <41603@sgi.sgi.com>
Organization: HP Lake Stevens, WA
Lines: 36

This solution is probably specific to Silicon Graphics.  When I try it
on my HP CC 2.0 series300 implementation, I get:

% CC -signed signed.c

CC signed.c:
"signed.c", line 5: warning: " signed" not implemented (ignored)
cc -signed signed.i -lC
cc: (warning) unrecognized option -i
cc: (warning) unrecognized option -e
cc: (warning) unrecognized option -d
cc: (warning) unrecognized option -i
cc: (warning) unrecognized option -e
cc: (warning) unrecognized option -d
cc: (warning) unrecognized option -i
cc: (warning) unrecognized option -e
cc: (warning) unrecognized option -d

ld: interrupt
ld: (Warning) did not generate an output file

...where signed.c is:

#include <stdio.h>

void main()
{
  signed char c = -10;
  printf("%d\n",c);
}

On this machine, apparently CC rejects the "signed" keyword, replacing it
with null, generates an unnecessary warning message, then passes the 
equivalent "C" code to the backend compiler, which has "signed" chars
by default, and thus [in this case at least] actually generates what was
called for.  End score: 0 compilation errors, 1 erroneous warning message.