Path: utzoo!utgpu!water!watmath!clyde!att-cb!ihnp4!inuxc!iuvax!pur-ee!uiucdcs!uxc.cso.uiuc.edu!ccvaxa!aglew
From: aglew@ccvaxa.UUCP
Newsgroups: comp.arch
Subject: Re: RISC data alignment
Message-ID: <28200109@ccvaxa>
Date: 24 Feb 88 17:02:00 GMT
References: <2710@mmintl.UUCP>
Lines: 9
Nf-ID: #R:mmintl.UUCP:2710:ccvaxa:28200109:000:472
Nf-From: ccvaxa.UUCP!aglew    Feb 24 11:02:00 1988


>That's not a good example of the type of code that would break.  I use
>the ordering property of structs to hide data.  If I have a struct which
>has some house keeping at the end of the struct, I don't have to tell
>the rest of the modules about it.  e.g.

But K&R don't guarantee that struct { int; short; int; } will have fields
in the same place as struct { int; short; } (or I'm sure that someone will
give me chapter and verse), so this code isn't portable anyway.