From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:42405) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ScevQ-0006wS-Nl for qemu-devel@nongnu.org; Thu, 07 Jun 2012 11:47:09 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ScevM-000801-JS for qemu-devel@nongnu.org; Thu, 07 Jun 2012 11:47:04 -0400 Received: from mail-pz0-f45.google.com ([209.85.210.45]:50011) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ScevM-0007zf-AO for qemu-devel@nongnu.org; Thu, 07 Jun 2012 11:47:00 -0400 Received: by dadv2 with SMTP id v2so1161303dad.4 for ; Thu, 07 Jun 2012 08:46:58 -0700 (PDT) Sender: Paolo Bonzini Message-ID: <4FD0CCED.3000702@redhat.com> Date: Thu, 07 Jun 2012 17:46:53 +0200 From: Paolo Bonzini MIME-Version: 1.0 References: <4FCE7684.2070206@redhat.com> <4FCF5512.9000704@redhat.com> <4FCF5BA8.3010201@suse.de> <4FCF64E4.50701@redhat.com> <20120606151640.GA7733@illuin> <4FCF777B.7000806@redhat.com> <20120606161446.GC7733@illuin> <4FCF8A0F.3020306@redhat.com> <20120606200907.GQ2916@illuin> <4FD090B2.4090305@redhat.com> <20120607152928.GU2916@illuin> In-Reply-To: <20120607152928.GU2916@illuin> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH 00/16] introduce OptsVisitor, rebase -net/-netdev parsing List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Michael Roth Cc: Laszlo Ersek , =?ISO-8859-1?Q?Andreas_F=E4rber?= , qemu-devel@nongnu.org Il 07/06/2012 17:29, Michael Roth ha scritto: > For QEMU <-> X serialization/deserialization, such as a visitor which > implements a wire encoding (QMP being the only example currently), we need to > take care that the wire encoding is compatible with the representation > expected by the other end (according to the QAPI schema or whatever other > means we use to document it). This holds for QMP/JSON, and we'll need to take > care that it holds for anything that's added in the future. Actually the string visitor does indeed need an uint64 visitor exactly for this reason. Will be done before 1.2. :) Laszlo's option visitor needs the same, but it's not in the tree. Paolo