Re: [Qemu-devel] [PATCH 00/18] qom: dynamic properties and composition tree

[Avi Kivity]

On 12/01/2011 04:42 PM, Anthony Liguori wrote:
>
>>
>> We need good tools to allow easy review of the ABI bits hiding in
>> patches, and to maintain ABI compatibility.  Something like
>> qemu-print-abi that dumps all properties for all devices.  Patches could
>> show the ABI changes by including a diff of the output of this program
>> from before and after a change, and we could add similar tests for
>> backwards compatibility.
>
> I'm not sure that we want this interface to be backwards compatible. 
> I actually think we should provide a higher level interface that's
> explicitly there for compatibility.  Probably in the form of a C
> library that can be documented and reasoned with better.
>

Does this force anyone who wants a stable ABI to use this library?

I don't have a good picture of this library.  If FooState has a bar
propery, do you generate qemu_foo_get_bar() and qemu_foo_set_bar()
accessors?

-- 
error compiling committee.c: too many arguments to function