Date: Fri, 10 Jun 2005 11:16:27 +0200 From: Stefan Farfeleder <stefan@fafoe.narf.at> To: Dag-Erling =?iso-8859-1?Q?Sm=F8rgrav?= <des@des.no> Cc: current@freebsd.org Subject: Re: [current tinderbox] failure on ...all... Message-ID: <20050610091624.GA35628@wombat.fafoe.narf.at> In-Reply-To: <863brqy41j.fsf@xps.des.no> References: <20050609234619.AD1F67306E@freebsd-current.sentex.ca> <p0621025fbeceac0673f8@128.113.24.47> <84dead720506091950779d1661@mail.gmail.com> <86oeae3d8f.fsf@xps.des.no> <84dead72050610001675a32c19@mail.gmail.com> <863brq3bbz.fsf@xps.des.no> <84dead7205061001534b9385b3@mail.gmail.com> <863brqy41j.fsf@xps.des.no>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Jun 10, 2005 at 11:06:16AM +0200, Dag-Erling Smørgrav wrote:
> Joseph Koshy <joseph.koshy@gmail.com> writes:
> > Dag-Erling Smørgrav <des@des.no> writes:
> > > It also seems strange to me that you on the one hand introduce a
> > > new struct to separate MD and MI interfaces, and on the other hand
> > > continue to assume that they are assignment-compatible.
> > I'd be very surprised if two C structures with identical definitions
> > were not assignment compatible.
>
> I wouldn't be surprised if the standard says they aren't.
> Unfortunately, my copy is at home.
Do you mean the following?
struct t1 { int a; } x;
struct t2 { int a; } y = { 42 };
x = y;
The types `struct t1' and `struct t2' are not compatible and thus not
assignable. See 6.2.7 and 6.5.16.1.
Stefan
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050610091624.GA35628>