From: Ethan Grammatikidis <eekee57@fastmail.fm>
To: 9fans@9fans.net
Subject: Re: [9fans] C compiler question
Date: Wed, 15 Jul 2009 12:34:36 +0100 [thread overview]
Message-ID: <20090715123436.f9edec2a.eekee57@fastmail.fm> (raw)
In-Reply-To: <dd6fe68a0907141245g657b7abdh29b825f62951f1c4@mail.gmail.com>
On Tue, 14 Jul 2009 12:45:56 -0700
Russ Cox <rsc@swtch.com> wrote:
> enough.
>
> there was a bug, plain and simple.
>
> struct T {
> struct S s;
> };
>
> is not valid. never was, never will be.
> fix the compiler already.
Newbie question: Does this statement apply to any struct S (meaning you can never have a struct as member of another struct), or does it only apply in cases where the structure of S is not known at that point?
--
Ethan Grammatikidis
Those who are slower at parsing information must
necessarily be faster at problem-solving.
next prev parent reply other threads:[~2009-07-15 11:34 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
2009-07-14 19:29 ` erik quanstrom
2009-07-14 19:45 ` Russ Cox
2009-07-15 11:34 ` Ethan Grammatikidis [this message]
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=20090715123436.f9edec2a.eekee57@fastmail.fm \
--to=eekee57@fastmail.fm \
--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).