Eric Blake 7a82e7ff73 qapi: Check for member name conflicts with a base class ... Our type inheritance for both 'struct' and for flat 'union' merges key/value pairs from the base class with those from the type in question. Although the C code currently boxes things so that there is a distinction between which member is referred to, the QMP wire format does not allow passing a key more than once in a single object. Besides, if we ever change the generated C code to not be quite so boxy, we'd want to avoid duplicate member names there, too. Fix a testsuite entry added in an earlier patch, as well as adding a couple more tests to ensure we have appropriate coverage. Ensure that collisions are detected, regardless of whether there is a difference in opinion on whether the member name is optional. Backports commit ff55d72eaf9628e7d58e7b067b361cdbf789c9f4 from qemu		2018-02-19 14:38:46 -05:00
..
create_config	more cleanup qemu/configure	2017-01-19 14:11:54 +08:00
make_device_config.sh
ordereddict.py
qapi-event.py	qapi: Drop support for inline nested types	2018-02-19 14:30:36 -05:00
qapi-types.py	qapi: Drop support for inline nested types	2018-02-19 14:30:36 -05:00
qapi-visit.py	qapi: Drop dead visitor code related to nested structs	2018-02-19 14:35:55 -05:00
qapi.py	qapi: Check for member name conflicts with a base class	2018-02-19 14:38:46 -05:00