David Hildenbrand writes:
> On 15.11.18 10:48, Markus Armbruster wrote:
>> David Hildenbrand writes:
>>
>>> On 14.11.18 18:38, Markus Armbruster wrote:
David Hildenbrand writes:
> The input visitor has some problems right now, especially
> - unsigned type "Range" is used to p
On 15.11.18 10:48, Markus Armbruster wrote:
> David Hildenbrand writes:
>
>> On 14.11.18 18:38, Markus Armbruster wrote:
>>> David Hildenbrand writes:
>>>
The input visitor has some problems right now, especially
- unsigned type "Range" is used to process signed ranges, resulting in
>>
David Hildenbrand writes:
> On 14.11.18 18:38, Markus Armbruster wrote:
>> David Hildenbrand writes:
>>
>>> 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
>>>
On 14.11.18 18:38, Markus Armbruster wrote:
> David Hildenbrand writes:
>
>> 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,
David Hildenbrand writes:
> 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 err
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
