Date: Mon, 2 Jun 1997 18:00:55 +0930 (CST) From: Michael Smith <msmith@atrad.adelaide.edu.au> To: un_x@anchorage.net (Steve Howe) Cc: mellon@pobox.com, hackers@FreeBSD.ORG Subject: Re: signed/unsigned cpp Message-ID: <199706020830.SAA21068@genesis.atrad.adelaide.edu.au> In-Reply-To: <Pine.BSF.3.95q.970601234922.1753E-100000@aak.anchorage.net> from Steve Howe at "Jun 1, 97 11:55:29 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
Steve Howe stands accused of saying: > > > 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" ... ... because it is not possible to tell _which_one_ of the two it will be like in all cases. -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199706020830.SAA21068>