Path: utzoo!utgpu!watserv1!watmath!att!att!dptg!ulysses!andante!mit-eddie!wuarchive!julius.cs.uiuc.edu!psuvax1!rutgers!cmcl2!kramden.acf.nyu.edu!brnstnd
From: brnstnd@kramden.acf.nyu.edu (Dan Bernstein)
Newsgroups: comp.std.c
Subject: Re: X3J11 Pleasanton meeting summary
Message-ID: <21360:Oct1820:21:0490@kramden.acf.nyu.edu>
Date: 18 Oct 90 20:21:04 GMT
References: <14061@smoke.BRL.MIL> <14005:Oct1801:26:5890@kramden.acf.nyu.edu> <14181@smoke.BRL.MIL>
Organization: IR
Lines: 20

In article <14181@smoke.BRL.MIL> gwyn@smoke.BRL.MIL (Doug Gwyn) writes:
> In article <14005:Oct1801:26:5890@kramden.acf.nyu.edu> brnstnd@kramden.acf.nyu.edu (Dan Bernstein) writes:
> >In article <14061@smoke.BRL.MIL> gwyn@smoke.BRL.MIL (Doug Gwyn) writes:
> >> In article <7944:Oct906:02:0690@kramden.acf.nyu.edu> brnstnd@kramden.acf.nyu.edu (Dan Bernstein) writes:
> >> >  x is of type char [100][3],    sizeof(x) is 400
> >> Not permitted.  sizeof x is required to be 300.
> >... is there any portable way to get around this restriction?
> What on earth are you talking about?  It's a restriction on the
> implementation, not on a program.

Exactly. I want to give away some rights, and let the compiler do a
better job by allocating an extra byte for each element of x. In other
words, I want to get around this restriction.

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.

---Dan