Xref: utzoo comp.lang.c:12493 comp.arch:6306
Path: utzoo!attcan!uunet!husc6!rutgers!tut.cis.ohio-state.edu!bloom-beacon!mcgill-vision!mouse
From: mouse@mcgill-vision.UUCP (der Mouse)
Newsgroups: comp.lang.c,comp.arch
Subject: Re: Explanation, please!
Message-ID: <1310@mcgill-vision.UUCP>
Date: 11 Sep 88 11:08:50 GMT
References: <638@paris.ics.uci.edu> <dpmuY#2EBC4R=eric@snark.UUCP> <339@quintus.UUCP>
Organization: McGill University, Montreal
Lines: 17

In article <339@quintus.UUCP>, jabir@quintus.uucp (Jabir Hussain) writes:
> In article <9064@pur-ee.UUCP> hankd@pur-ee.UUCP (Hank Dietz) writes:
>>		*(((struct t512 *) q)++) = *(((struct t512 *) p)++);
>>	but, for some unknown reason, the VAX C compiler didn't like that.

> one portable way around that is to do something like:
[summarized]
> union { struct { int t[512]; } *t512; ...; char *caddr; }
[then use ++ on .t512]

This falls hopelessly flat if char * and struct {...} * have
significantly different representation.

					der Mouse

			old: mcgill-vision!mouse
			new: mouse@larry.mcrcim.mcgill.edu