From: "Ronald G. Minnich" <rminnich@lanl.gov>
To: David Leimbach <leimy2k@gmail.com>,
Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] 8c question
Date: Tue, 5 Jul 2005 08:47:07 -0600 [thread overview]
Message-ID: <Pine.LNX.4.58.0507050846070.30613@enigma.lanl.gov> (raw)
In-Reply-To: <3e1162e6050704193649539ee@mail.gmail.com>
On Mon, 4 Jul 2005, David Leimbach wrote:
> On 7/2/05, Charles Forsyth <forsyth@terzarima.net> wrote:
> > >>it cant be worked around without breaking the cross
> > >>platform features of their headers.
> >
> > sounds brilliantly portable to me.
> > what do they do? insert 0-length padding areas
> > to make these structures `portable'?
> >
> >
> Yeah, it's undefined what happens if a struct is empty in C99. Seems a
> really silly thing for someone to rely on. What are they trying to
> accomplish? The only thing I can think of is some kind of type safety
> based on a tag generated for a unique "struct". They should probably
> make it wrap a void * or something.
>
IIRC this is one of those deals where people do something liiek:
struct element {
int x,y;
};
struct a {
int numelements;
struct elements blah[0];
};
is that it Tim? I might be wrong on this.
It's not reliable in gcc, as we found out the hard way on the linuxbios
project ...
ron
next prev parent reply other threads:[~2005-07-05 14:47 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-01 23:17 Tim Newsham
2005-07-02 12:43 ` Charles Forsyth
2005-07-05 2:36 ` David Leimbach
2005-07-05 14:47 ` Ronald G. Minnich [this message]
2005-07-05 15:27 ` Latchesar Ionkov
2005-07-05 15:33 ` Ronald G. Minnich
2005-07-05 18:33 ` Tim Newsham
2005-07-05 15:35 ` David Leimbach
2005-07-07 23:08 ` Charles Forsyth
2005-07-08 0:06 ` Ronald G. Minnich
2005-07-08 0:27 ` Russ Cox
2005-07-08 14:36 ` Ronald G. Minnich
2005-07-08 19:03 ` jmk
2005-07-08 19:40 ` Charles Forsyth
2005-07-09 1:02 ` Ronald G. Minnich
2005-07-08 3:31 ` Tim Newsham
2005-07-08 11:14 ` Charles Forsyth
2005-07-09 1:04 ` Tim Newsham
2005-07-09 9:40 ` Charles Forsyth
2005-07-11 0:57 ` Ronald G. Minnich
2005-07-11 1:26 ` [9fans] Xen comms Tim Newsham
2005-07-11 19:21 ` Eric Van Hensbergen
2005-07-11 19:23 ` [9fans] 8c question Eric Van Hensbergen
2005-07-11 19:58 ` Ronald G. Minnich
2005-07-11 20:05 ` Eric Van Hensbergen
2005-07-11 20:15 ` Ronald G. Minnich
2005-07-11 20:35 ` Eric Van Hensbergen
2005-07-11 20:38 ` Ronald G. Minnich
2005-07-11 21:03 ` Eric Van Hensbergen
2005-07-11 21:09 ` Ronald G. Minnich
2005-07-11 21:13 ` Eric Van Hensbergen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.58.0507050846070.30613@enigma.lanl.gov \
--to=rminnich@lanl.gov \
--cc=9fans@cse.psu.edu \
--cc=leimy2k@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).