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/a101de2ff0781795f4f7c64ece6e3d48b5783627
It'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
