David Hildenbrand writes:
> On 20.11.18 21:58, Markus Armbruster wrote:
>> I think the title should be something like
>>
>> qapi: Rewrite string-input-visitor's integer and list parsing
>>
>> because you don't actually rewrite all of it.
>>
>> Eric Blake writes:
>>
>>> On 11/20/18 3:25 A
On 20.11.18 21:58, Markus Armbruster wrote:
> I think the title should be something like
>
> qapi: Rewrite string-input-visitor's integer and list parsing
>
> because you don't actually rewrite all of it.
>
> Eric Blake writes:
>
>> On 11/20/18 3:25 AM, David Hildenbrand wrote:
>>> The inp
I think the title should be something like
qapi: Rewrite string-input-visitor's integer and list parsing
because you don't actually rewrite all of it.
Eric Blake writes:
> On 11/20/18 3:25 AM, David Hildenbrand wrote:
>> The input visitor has some problems right now, especially
>> - unsign
On 11/20/18 3:25 AM, David Hildenbrand wrote:
The input visitor has some problems right now, especially
- unsigned type "Range" is used to process signed ranges, resulting in
inconsistent behavior and ugly/magical code
- uint64_t are parsed like int64_t, so big uint64_t values are not
suppo
The input visitor has some problems right now, especially
- unsigned type "Range" is used to process signed ranges, resulting in
inconsistent behavior and ugly/magical code
- uint64_t are parsed like int64_t, so big uint64_t values are not
supported and error messages are misleading
- lists/ran