On 04/28/2016 07:06 AM, Markus Armbruster wrote:
> Eric Blake writes:
>
>> Rather than having two separate ways to create a QMP input
>> visitor, where the safer approach has the more verbose name,
>> it is better to consolidate things into a single function
>> where the caller must explicitly ch
Eric Blake writes:
> Rather than having two separate ways to create a QMP input
> visitor, where the safer approach has the more verbose name,
> it is better to consolidate things into a single function
> where the caller must explicitly choose whether to be strict
> or to ignore excess input. U
Rather than having two separate ways to create a QMP input
visitor, where the safer approach has the more verbose name,
it is better to consolidate things into a single function
where the caller must explicitly choose whether to be strict
or to ignore excess input. Use strict mode in more places o
