Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watnot!watmath!clyde!cbatt!ihnp4!ptsfa!lll-lcc!mordor!sri-spam!sri-unix!husc6!ut-sally!ut-ngp!dlnash
From: dlnash@ut-ngp.UUCP
Newsgroups: comp.lang.c
Subject: Re: Value of x?
Message-ID: <4927@ut-ngp.UUCP>
Date: Wed, 1-Apr-87 11:11:19 EST
Article-I.D.: ut-ngp.4927
Posted: Wed Apr  1 11:11:19 1987
Date-Received: Sat, 4-Apr-87 07:17:53 EST
References: <6570@brl-adm.ARPA> <705@brl-sem.ARPA>
Organization: UTexas Computation Center, Austin, Texas
Lines: 25

In article <705@brl-sem.ARPA>, ron@brl-sem.ARPA (Ron Natalie <ron>) writes:
> In article <6570@brl-adm.ARPA>, @relay.cs.net> writes:
> 
> > In the Microsoft C compiler V4.0, '\x' is compiled as 0 on the
> > grounds that it's a brain-damaged version of '\x00'.  This is what
> > Microsoft's support group said when I reported what I thought was a 
> > bug.  I claim that '\x' is a perfectly fine representation of the 
> > character x and should have value 120 base 10.  How sayeth INFO-C?
> 
> Neither \x meaning 0 nor \x meaning 'x' is correct.  There is no meaning
> to \x and those who use it are asking for trouble.  By your own admission
> \n should be the character n which we all know is not true.


K&R p.181:  "If the character following a backslash is not one of those
            specified [the specified characters are n, t, b, r, f, \, ',
            and ddd (three octal digits) -ed.], the backslash is ignored."


				Don Nash

UUCP:    ...!{ihnp4, allegra, seismo!ut-sally}!ut-ngp!dlnash
ARPA:    dlnash@ngp.UTEXAS.EDU
BITNET:	 CCEU001@UTADNX, DLNASH@UTADNX
TEXNET:  UTADNX::CCEU001, UTADNX::DLNASH