Eric Blake writes:
> On 10/27/2015 02:21 AM, Markus Armbruster wrote:
>> Eric Blake writes:
>>
>>> Now that we have separated union tag values from colliding with
>>> non-variant C names, by naming the union 'u', we should reserve
>>> this name for our use. Note that we want to forbid 'u' even
On 10/27/2015 02:21 AM, Markus Armbruster wrote:
> Eric Blake writes:
>
>> Now that we have separated union tag values from colliding with
>> non-variant C names, by naming the union 'u', we should reserve
>> this name for our use. Note that we want to forbid 'u' even in
>> a struct with no vari
Eric Blake writes:
> Now that we have separated union tag values from colliding with
> non-variant C names, by naming the union 'u', we should reserve
> this name for our use. Note that we want to forbid 'u' even in
> a struct with no variants, because it is possible for a future
> qemu release
Now that we have separated union tag values from colliding with
non-variant C names, by naming the union 'u', we should reserve
this name for our use. Note that we want to forbid 'u' even in
a struct with no variants, because it is possible for a future
qemu release to extend QMP in a backwards-co
