[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] [PATCH RFC 2/6] qapi: use qemu_strtod() in string-input
From: |
David Hildenbrand |
Subject: |
Re: [Qemu-devel] [PATCH RFC 2/6] qapi: use qemu_strtod() in string-input-visitor |
Date: |
Thu, 15 Nov 2018 14:54:04 +0100 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.3.0 |
On 15.11.18 14:17, Eric Blake wrote:
> On 11/15/18 5:09 AM, David Hildenbrand wrote:
>
>>> Three more: in qobject-input-visitor.c's
>>> qobject_input_type_number_keyval(),
>>
>> This one is interesting, as it properly bails out when parsing "inf"
>> (via isFinite()). - should we do the same for the string input visitor?
>>
>> Especially, should we forbid "inf" and "NaN" in both scenarios?
>
> JSON can't represent non-finite doubles. Internally, we might be able to
> use them, but you have a point that consistently rejecting non-finite in
> all of our QAPI parsers makes it easier to reason about the code base
> (the command line can't be used to inject a value not possible via QMP).
> So that makes sense to me. qemu_strtod() shouldn't reject non-finite
> numbers (because it is useful for more than just qapi), but we could add
> a new qemu_strtod_finite() if that would help avoid duplication.
>
Yes, I'll exactly add that! Thanks
--
Thanks,
David / dhildenb
[Qemu-devel] [PATCH RFC 4/6] test-string-input-visitor: use virtual walk, David Hildenbrand, 2018/11/09
[Qemu-devel] [PATCH RFC 6/6] test-string-input-visitor: add range overflow tests, David Hildenbrand, 2018/11/09
[Qemu-devel] [PATCH RFC 5/6] test-string-input-visitor: split off uint64 list tests, David Hildenbrand, 2018/11/09
[Qemu-devel] [PATCH RFC 1/6] cutils: add qemu_strtod(), David Hildenbrand, 2018/11/09
[Qemu-devel] [PATCH RFC 3/6] qapi: rewrite string-input-visitor, David Hildenbrand, 2018/11/09