Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!uakari.primate.wisc.edu!uflorida!haven!adm!smoke!gwyn
From: gwyn@smoke.BRL.MIL (Doug Gwyn)
Newsgroups: comp.std.c
Subject: Re: X3J11 Pleasanton meeting summary
Message-ID: <14191@smoke.BRL.MIL>
Date: 18 Oct 90 20:55:41 GMT
References: <14005:Oct1801:26:5890@kramden.acf.nyu.edu> <14181@smoke.BRL.MIL> <21360:Oct1820:21:0490@kramden.acf.nyu.edu>
Organization: U.S. Army Ballistic Research Laboratory, APG, MD.
Lines: 8

In article <21360:Oct1820:21:0490@kramden.acf.nyu.edu> brnstnd@kramden.acf.nyu.edu (Dan Bernstein) writes:
>What I'm really trying to ask is whether my only choice is to count
>bytes manually, assume fixed type sizes, and declare the right number of
>padding characters by hand. I'd rather let the compiler choose padding
>for me---it usually does a better job.

I don't see why you should even be thinking along these lines.  Surely
the compiler is going to generate reasonable code without your assistance.