From: Roman V Shaposhnik <rvs@sun.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] C compiler question
Date: Tue, 14 Jul 2009 11:59:34 -0700 [thread overview]
Message-ID: <1247597974.18344.5496.camel@work.SFBay.Sun.COM> (raw)
In-Reply-To: <21dabe281409184572838ffa29c8fe14@coraid.com>
On Tue, 2009-07-14 at 13:46 -0400, erik quanstrom wrote:
> > rejecting the struct seems like the right thing to do as per
> > ISO/IEC 9899:1999 (http://www.open-std.org/JTC1/SC22/wg14/www/docs/n1124.pdf)
> > sec. 6.7.2.1 para. 2
> >
> > "A structure or union shall not contain a member with incomplete or function type (hence,
> > a structure shall not contain an instance of itself, but may contain a pointer to an instance
> > of itself), except that the last member of a structure with more than one named member
> > may have incomplete array type; such a structure (and any union containing, possibly
> > recursively, a member that is such a structure) shall not be a member of a structure or an
> > element of an array."
>
> you're implying that the point of the plan 9 compilers
> is to toe the c99 line.
For the dirty corner of any language one is usually better off with
a written formal standard. Now, since Plan9 doesn't have such a
document, relying on a work done by c99 committee would seem like
a wise thing to do.
And it is not like we are talking about C++ ISO standard here, the
C99 is actually quite beautiful (except may be a couple of places
like compound literals, and stuff).
What's your problem with such an approach?
> also, a pointer to an incomplete type is used
> in many places in plan 9 libraries.
The above paragraph has nothing to do with pointers to incomplete types
(except for a clarification). Why are you bringing this up?
Thanks,
Roman.
next prev parent reply other threads:[~2009-07-14 18:59 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-12 3:59 Adriano Verardo
2009-07-12 16:59 ` erik quanstrom
2009-07-14 2:58 ` Adriano Verardo
2009-07-14 3:14 ` erik quanstrom
2009-07-14 14:00 ` Adriano Verardo
2009-07-14 14:57 ` erik quanstrom
2009-07-14 16:26 ` Adriano Verardo
2009-07-14 16:38 ` erik quanstrom
2009-07-14 17:18 ` Roman V Shaposhnik
2009-07-14 17:46 ` erik quanstrom
2009-07-14 18:59 ` Roman V Shaposhnik [this message]
2009-07-14 19:29 ` erik quanstrom
2009-07-14 19:45 ` Russ Cox
2009-07-15 11:34 ` Ethan Grammatikidis
2009-07-15 11:38 ` erik quanstrom
2009-07-14 20:28 ` [9fans] pointers to incomplete types Roman V Shaposhnik
2009-07-15 9:25 ` [9fans] C compiler question robert wilson
2009-07-14 4:00 ` Russ Cox
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=1247597974.18344.5496.camel@work.SFBay.Sun.COM \
--to=rvs@sun.com \
--cc=9fans@9fans.net \
/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).