@@ -106,17 +106,8 @@ struct %(c_name)s {
''',
c_type=c_name(variants.tag_member.type.name))
- # FIXME: What purpose does data serve, besides preventing a union that
- # has a branch named 'data'? We use it in qapi-visit.py to decide
- # whether to bypass the switch statement if visiting the discriminator
- # failed; but since we 0-initialize structs, and cannot tell what
- # branch of the union is in use if the discriminator is invalid, there
- # should not be any data leaks even without a data pointer. Or, if
- # 'data' is merely added to guarantee we don't have an empty union,
- # shouldn't we enforce that at .json parse time?
ret += mcgen('''
union { /* union tag is @%(c_name)s */
- void *data;
''',
c_name=c_name((variants.tag_member and
variants.tag_member.name) or 'type'))
@@ -81,7 +81,7 @@
'number': ['number'],
'boolean': ['bool'],
'string': ['str'],
- 'sizes': ['size'] } }
+ 'data': ['size'] } }
# testing commands
{ 'command': 'user_def_cmd', 'data': {} }
@@ -119,8 +119,8 @@ object UserDefNativeListUnion
case number: :obj-numberList-wrapper
case boolean: :obj-boolList-wrapper
case string: :obj-strList-wrapper
- case sizes: :obj-sizeList-wrapper
-enum UserDefNativeListUnionKind ['integer', 's8', 's16', 's32', 's64', 'u8', 'u16', 'u32', 'u64', 'number', 'boolean', 'string', 'sizes']
+ case data: :obj-sizeList-wrapper
+enum UserDefNativeListUnionKind ['integer', 's8', 's16', 's32', 's64', 'u8', 'u16', 'u32', 'u64', 'number', 'boolean', 'string', 'data']
object UserDefOne
base UserDefZero
member string: str optional=False
Now that we no longer have any clients of the 'void *data' member injected into unions, we can drop it. Update the testsuite to prove that we no longer have a name collision. Signed-off-by: Eric Blake <eblake@redhat.com> --- scripts/qapi-types.py | 9 --------- tests/qapi-schema/qapi-schema-test.json | 2 +- tests/qapi-schema/qapi-schema-test.out | 4 ++-- 3 files changed, 3 insertions(+), 12 deletions(-)