From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:41906)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <berto@igalia.com>) id 1YiJSU-0003Vh-U2
	for qemu-devel@nongnu.org; Wed, 15 Apr 2015 05:18:11 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <berto@igalia.com>) id 1YiJSP-0005J2-Gd
	for qemu-devel@nongnu.org; Wed, 15 Apr 2015 05:18:10 -0400
Received: from smtp3.mundo-r.com ([212.51.32.191]:14015 helo=smtp4.mundo-r.com)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <berto@igalia.com>) id 1YiJSP-0005H6-AA
	for qemu-devel@nongnu.org; Wed, 15 Apr 2015 05:18:05 -0400
From: Alberto Garcia <berto@igalia.com>
In-Reply-To: <55285792.70103@redhat.com>
References: <1427995743-7865-1-git-send-email-armbru@redhat.com>
	<1427995743-7865-20-git-send-email-armbru@redhat.com>
	<55285792.70103@redhat.com>
Date: Wed, 15 Apr 2015 11:16:58 +0200
Message-ID: <w51r3rl21kl.fsf@maestria.local.igalia.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Subject: Re: [Qemu-devel] [PATCH RFC 19/19] qapi: New QMP command
	query-schema for QMP schema introspection
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>, Markus Armbruster <armbru@redhat.com>, qemu-devel@nongnu.org
Cc: kwolf@redhat.com, akong@redhat.com, mdroth@linux.vnet.ibm.com

On Sat 11 Apr 2015 01:06:58 AM CEST, Eric Blake <eblake@redhat.com> wrote:

>> +{ 'type': 'SchemaInfoEnum',
>> +  'data': { 'values': ['str'] } }
>
> At one point, one thread suggested that we might want to allow QAPI to
> support enums with fixed values, as in:
>
> 'data': [ {'one': 1}, {'three': 3} ]

Out of curiosity, what's the use case for that?

Berto