Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!ccu.umanitoba.ca!herald.usask.ca!alberta!ubc-cs!uw-beaver!cornell!batcomputer!caen!uakari.primate.wisc.edu!samsung!uunet!decwrl!deccrl!news.crl.dec.com!nntpd.lkg.dec.com!tkou02.enet.dec.com!jit533!diamond From: diamond@jit533.swstokyo.dec.com (Norman Diamond) Newsgroups: comp.std.c Subject: Re: call to revolt Message-ID: <1991Jun28.040639.28830@tkou02.enet.dec.com> Date: 28 Jun 91 04:06:39 GMT References: <992@baby.and.nl> <1991Jun27.002412.10929@tkou02.enet.dec.com> <4247@ksr.com> Sender: usenet@tkou02.enet.dec.com (USENET News System) Reply-To: diamond@jit533.enet@tkou02.enet.dec.com (Norman Diamond) Organization: Digital Equipment Corporation Japan , Tokyo Lines: 21 In article <4247@ksr.com> jfw@ksr.com (John F. Woods) writes: >diamond@jit533.swstokyo.dec.com (Norman Diamond) writes: >>In article <992@baby.and.nl> jos@and.nl (J. Horsmeier) writes: >>>Hi there, I'll die if casting lvals is going to be illegal. >>>type* Thing; >>>((int)Thing)= Thing-Base+1; >>You'll die if you have to write >> Thing = (type*) (Thing-Base+1); >>My heart bleeds for you. > >Well, in fact, the second line isn't actually obligated to do what is >apparently desired, i.e. to copy the integer value bit-for-bit into the >pointer; Yeah, well neither is the first line. The first line intuitively should not copy anything at all into the pointer, and legally can erase his hard disk after issuing a diagnostic. -- Norman Diamond diamond@tkov50.enet.dec.com If this were the company's opinion, I wouldn't be allowed to post it. Permission is granted to feel this signature, but not to look at it.