Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!bloom-beacon!oberon!skat.usc.edu!blarson
From: blarson@skat.usc.edu (Bob Larson)
Newsgroups: comp.std.c
Subject: Re: The \c escape
Message-ID: <10051@oberon.USC.EDU>
Date: 22 Jun 88 22:40:18 GMT
References: <4604@haddock.ISC.COM> <5907@umn-cs.cs.umn.edu> <8125@brl-smoke.ARPA> <8127@brl-smoke.ARPA> <963@ficc.UUCP>
Sender: news@oberon.USC.EDU
Reply-To: blarson@skat.usc.edu (Bob Larson)
Organization: USC AIS, Los Angeles
Lines: 20

In article <963@ficc.UUCP> peter@ficc.UUCP (Peter da Silva) writes:
>(2) What's wrong with a readable and maintainable way of initialising a
>    32-bit unsigned integer to 0x464F524DL?
0x464F524DL
> You prefer that (or ('F'<<24)| ('O'<<16)|('R'<<8)|('M')) 
> to 'FORM'?

No, I use what I mean.  Are you trying to imply that the three
things you mention have the same value?  (I grant that on some
machines with some compilers they might.  I'm sure on other machines
and compilers they are different.)

Multi-character constants are "implemntation defined" (K&R2 page 193)
thus are for portable code UNDEFINED.

-- 
Bob Larson	Arpa: Blarson@Ecla.Usc.Edu	blarson@skat.usc.edu
Uucp: {sdcrdcf,cit-vax}!oberon!skat!blarson
Prime mailing list:	info-prime-request%ais1@ecla.usc.edu
			oberon!ais1!info-prime-request