From mboxrd@z Thu Jan  1 00:00:00 1970
Date: Wed, 15 Jul 2009 12:34:36 +0100
From: Ethan Grammatikidis <eekee57@fastmail.fm>
To: 9fans@9fans.net
Message-Id: <20090715123436.f9edec2a.eekee57@fastmail.fm>
In-Reply-To: <dd6fe68a0907141245g657b7abdh29b825f62951f1c4@mail.gmail.com>
References: <abc85ad6c854d3fc457396f6143aebc0@quanstro.net>
	<1247591909.18344.5479.camel@work.SFBay.Sun.COM>
	<21dabe281409184572838ffa29c8fe14@coraid.com>
	<1247597974.18344.5496.camel@work.SFBay.Sun.COM>
	<a53acd743c3a6f747bf168ee2d08a2d4@coraid.com>
	<dd6fe68a0907141245g657b7abdh29b825f62951f1c4@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Subject: Re: [9fans] C compiler question
Topicbox-Message-UUID: 2137416a-ead5-11e9-9d60-3106f5b1d025

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.