From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:57480)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <pbonzini@redhat.com>) id 1Uu3yC-0008I8-0u
	for qemu-devel@nongnu.org; Tue, 02 Jul 2013 13:02:25 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <pbonzini@redhat.com>) id 1Uu3yA-0001OY-LM
	for qemu-devel@nongnu.org; Tue, 02 Jul 2013 13:02:23 -0400
Received: from mx3-phx2.redhat.com ([209.132.183.24]:41934)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <pbonzini@redhat.com>) id 1Uu3yA-0001OD-CM
	for qemu-devel@nongnu.org; Tue, 02 Jul 2013 13:02:22 -0400
Date: Tue, 2 Jul 2013 13:01:21 -0400 (EDT)
From: Paolo Bonzini <pbonzini@redhat.com>
Message-ID: <1408396387.2128564.1372784481475.JavaMail.root@redhat.com>
In-Reply-To: <51D3035A.1060605@redhat.com>
References: <1371644677-11041-1-git-send-email-akong@redhat.com>
	<878v1pqak4.fsf@codemonkey.ws> <51D2F1B3.1080903@redhat.com>
	<20130702153945.GZ2524@redhat.com> <51D3035A.1060605@redhat.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Subject: Re: [Qemu-devel] [PATCH] full introspection support for QMP
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/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: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Eric Blake <eblake@redhat.com>
Cc: Anthony Liguori <aliguori@us.ibm.com>, mdroth <mdroth@linux.vnet.ibm.com>, qemu-devel@nongnu.org, armbru@redhat.com, lcapitulino@redhat.com, qiaonuohan@cn.fujitsu.com, Amos Kong <akong@redhat.com>

> > Arguably that rule of thumb would apply equally to the QEMU
> > build scripts which already parse qapi-schema.json. It could
> > be possible to normalize qapi-schema.json somewhat to remove
> > this 2-stage parsing if we went down this route.
> 
> Indeed, I wouldn't mind a one-time pass over qapi-schema.json to make it
> follow a more rigid format if that made it easier to use it as-is with
> less post-processing.  It won't be very nice to backport such a
> conversion, but I don't know how much distros are planning on
> backporting introspection in the first place.

How would the schema look like after this "one-time pass"?

This:

> [
>          { "name": "protocol",
>            "type": "str" },
>          { "name": "fdname",
>            "type": "str" },
>          { "name": "skipauth",
>            "type": "bool",
>            "optional": true },
>          { "name": "tls",
>            "type": "bool",
>            "optional": true }
> ]

Looks quite awful for a human to write and read.

Paolo