Date: Sun, 1 Jun 1997 23:55:29 -0800 (AKDT) From: Steve Howe <un_x@anchorage.net> To: Anatoly Vorobey <mellon@pobox.com> Cc: freebsd-hackers <hackers@freebsd.org> Subject: Re: signed/unsigned cpp Message-ID: <Pine.BSF.3.95q.970601234922.1753E-100000@aak.anchorage.net> In-Reply-To: <19970601100320.37936@techunix.technion.ac.il>
next in thread | previous in thread | raw e-mail | index | archive | help
> The type `char' is always a distinct type from each of `signed > char' or `unsigned char', even though its behavior is always just > like one of those two. ok, but why? i'm trying to understand any possible reason for this, and can't think of any ... (my teachers used to hate me :) i've written assemblers and mini-compilers and have some understanding of what's necessary, but i don't get this! what's is the point of this rule? as it says, "its behaviour is always just like on of those two" ... > gcc is probably acting up because you specified a fascistic > warning level ;) In fact I just tried to reproduce it and -Wall > -pedantic did the trick, while -Wall by itself or even with > -ansi wasn't enough. no, just c++, i used no options. ------------------------------------------------------------------------- Sleep: a sign a caffeine deprivation ... http://www.anchorage.net/~un_x -------------------------------------------------------------------------
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.95q.970601234922.1753E-100000>