Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!wuarchive!psuvax1!hsdndev!cmcl2!adm!smoke!gwyn
From: gwyn@smoke.brl.mil (Doug Gwyn)
Newsgroups: comp.lang.c
Subject: Re: 0xFF != '\xFF' ?
Message-ID: <15779@smoke.brl.mil>
Date: 10 Apr 91 04:36:35 GMT
References: <28007837.35A9@marob.uucp>
Organization: U.S. Army Ballistic Research Laboratory, APG, MD.
Lines: 6

In article <28007837.35A9@marob.uucp> daveh@marob.uucp (Dave Hammond) writes:
>Is this because the '\nnn' token being seen as a char value and chars are
>signed on the machines I tested on?

Essentially, yes.  The value 255 gets stuffed into a char then converted
to type int, which propagates the sign bit when char acts as a signed type.