From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:52543) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Sdyvf-0006ZR-Ma for qemu-devel@nongnu.org; Mon, 11 Jun 2012 03:20:48 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1SdyvY-0007EL-OU for qemu-devel@nongnu.org; Mon, 11 Jun 2012 03:20:47 -0400 Received: from mx1.redhat.com ([209.132.183.28]:9468) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SdyvY-0007EE-GX for qemu-devel@nongnu.org; Mon, 11 Jun 2012 03:20:40 -0400 Message-ID: <4FD59C3F.2020306@redhat.com> Date: Mon, 11 Jun 2012 09:20:31 +0200 From: Paolo Bonzini MIME-Version: 1.0 References: <1338858018-17189-1-git-send-email-mdroth@linux.vnet.ibm.com> <1338858018-17189-2-git-send-email-mdroth@linux.vnet.ibm.com> <4FD59AA2.3000707@suse.de> In-Reply-To: <4FD59AA2.3000707@suse.de> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [Qemu-devel] [PATCH 01/17] qidl: add QEMU IDL processor List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: =?UTF-8?B?QW5kcmVhcyBGw6RyYmVy?= Cc: Peter Maydell , aliguori@us.ibm.com, quintela@redhat.com, Michael Roth , qemu-devel@nongnu.org, owasserm@redhat.com, akong@redhat.com, yamahata@valinux.co.jp Il 11/06/2012 09:13, Andreas F=C3=A4rber ha scritto: >>> >> +The first step is to move your device struct definition to a head= er file. This >>> >> +header file should only contain the struct definition and any pre= processor >>> >> +declarations you need to define the structure. This header file = will act as >>> >> +the source for the QC IDL compiler. >> >=20 >> > I don't think this is a fantastic idea -- the device struct should b= e >> > private to the device, and having it in a standalone header file is >> > asking for users of the device to illicitly include it and access >> > internals that they shouldn't. > But that is exactly where realize is headed. PCIBus, a9mp_priv etc. > structs will need to be made public so that they can be embedded. I thought that was just a convenience choice, not a necessity. The children objects could just as well be heap-allocated. Paolo