From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from [140.186.70.92] (port=52231 helo=eggs.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1PwhXX-0001Sz-5f
	for qemu-devel@nongnu.org; Mon, 07 Mar 2011 16:00:29 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <anthony@codemonkey.ws>) id 1PwhWU-0000FS-F3
	for qemu-devel@nongnu.org; Mon, 07 Mar 2011 15:59:23 -0500
Received: from mail-iy0-f173.google.com ([209.85.210.173]:40672)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <anthony@codemonkey.ws>) id 1PwhWU-0000FH-C4
	for qemu-devel@nongnu.org; Mon, 07 Mar 2011 15:59:22 -0500
Received: by iym7 with SMTP id 7so5168347iym.4
	for <qemu-devel@nongnu.org>; Mon, 07 Mar 2011 12:59:21 -0800 (PST)
Message-ID: <4D754724.4050601@codemonkey.ws>
Date: Mon, 07 Mar 2011 14:59:16 -0600
From: Anthony Liguori <anthony@codemonkey.ws>
MIME-Version: 1.0
Subject: Re: [Qemu-devel] [PATCH 00/22] QAPI Round 1
References: <1299460984-15849-1-git-send-email-aliguori@us.ibm.com>
	<AANLkTika3BkiECzQKrjUradj7zH+WrdunVR7EMvj8R8o@mail.gmail.com>
In-Reply-To: <AANLkTika3BkiECzQKrjUradj7zH+WrdunVR7EMvj8R8o@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: qemu-devel@nongnu.org, Adam Litke <aglitke@linux.vnet.ibm.com>, Markus Armbruster <armbru@redhat.com>, Luiz Capitulino <lcapitulino@redhat.com>

On 03/07/2011 09:08 AM, Stefan Hajnoczi wrote:
> The signals and slots magic makes sense when looking at the patches,
> but I wasn't confident about their semantics just by reading the
> documentation.  I had a vague idea about why the Event struct is
> needed but didn't fully understand.  Perhaps it's just me but I wanted
> to mention it in case you want to polish up that section.

This is the problem with writing documentation, it seems clear to me :-/

I'm not sure what bit of magic you're referring to.  Are you talking 
about the general rationale for why they they need to exist?  Or is it 
the way that they're supported with macro functions that seems confusing?

Regards,

Anthony Liguori