From owner-freebsd-current@FreeBSD.ORG  Fri Jun 10 09:16:33 2005
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
X-Original-To: current@freebsd.org
Delivered-To: freebsd-current@FreeBSD.ORG
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 0E79316A41C
	for <current@freebsd.org>; Fri, 10 Jun 2005 09:16:33 +0000 (GMT)
	(envelope-from stefan@fafoe.narf.at)
Received: from fafoe.narf.at (chello213047085026.6.14.vie.surfer.at
	[213.47.85.26]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9F46E43D4C
	for <current@freebsd.org>; Fri, 10 Jun 2005 09:16:32 +0000 (GMT)
	(envelope-from stefan@fafoe.narf.at)
Received: from wombat.fafoe.narf.at (wombat.fafoe.narf.at [192.168.1.42])
	by fafoe.narf.at (Postfix) with ESMTP id BF77F40AA;
	Fri, 10 Jun 2005 11:16:28 +0200 (CEST)
Received: by wombat.fafoe.narf.at (Postfix, from userid 1001)
	id 68CDDAE; Fri, 10 Jun 2005 11:16:27 +0200 (CEST)
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>
Message-ID: <20050610091624.GA35628@wombat.fafoe.narf.at>
Mail-Followup-To: Dag-Erling =?iso-8859-1?Q?Sm=F8rgrav?= <des@des.no>,
	Joseph Koshy <joseph.koshy@gmail.com>, current@freebsd.org
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>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <863brqy41j.fsf@xps.des.no>
User-Agent: Mutt/1.5.9i
Cc: current@freebsd.org
Subject: Re: [current tinderbox] failure on ...all...
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Jun 2005 09:16:33 -0000

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