|
From: | Anthony Liguori |
Subject: | Re: [Qemu-devel] Re: [PATCH 00/15] QAPI Round 1 (core code generator) (v2) |
Date: | Fri, 18 Mar 2011 09:22:25 -0500 |
User-agent: | Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.14) Gecko/20110223 Lightning/1.0b2 Thunderbird/3.1.8 |
On 03/18/2011 09:10 AM, Luiz Capitulino wrote:
IMO, what's happening here is that you want (or your focus is in) a different thing. Since the beginning we (Markus and I) have focused on having a flexible wire interface. In its most part, this requirement came from Avi (please Avi, correct me if I'm wrong), but of course that I agreed with it. You've said many times that you don't value non-C consumers that much, while our focus until today has been on higher level clients.
I realize that I've not been careful enough in my language. The problems I'm trying to address are just as applicable to non-C clients. In fact, I've written a Python client library that makes uses code generation:
http://repo.or.cz/w/qemu/aliguori.git/commit/a101de2ff0781795f4f7c64ece6e3d48b5783627It's much simpler than the C interfaces because Python has a bit more awesomeness than C.
The only properties of the Python interface that are different than the C is that adding optional parameters to a command handler works okay, but adding optional parameters to a signal still will not work.
Regards, Anthony Liguori
[Prev in Thread] | Current Thread | [Next in Thread] |