Eric Blake writes:
> On 11/19/2015 09:50 AM, Markus Armbruster wrote:
>> Let's think through this on a higher level.
>>
>> I figure the motivation for this patch is twofold:
>>
>> 1. C identifier clash detection
>>
>
>>
>> 2. Dislike for interfaces that differ only in case
>
> And the related
On 11/19/2015 09:50 AM, Markus Armbruster wrote:
> Let's think through this on a higher level.
>
> I figure the motivation for this patch is twofold:
>
> 1. C identifier clash detection
>
>
> 2. Dislike for interfaces that differ only in case
And the related dislike for interfaces that differ
Let's think through this on a higher level.
I figure the motivation for this patch is twofold:
1. C identifier clash detection
We generate C identifiers derived from QAPI names. These can clash
with (1) each other, (2) C keywords and selected other well-known
identifiers, and (3) the u
On 11/18/2015 01:53 AM, Eric Blake wrote:
> In general, designing user interfaces that rely on case
> distinction is poor practice. Another benefit of enforcing
> a restriction against case-insensitive clashes is that we
> no longer have to worry about the situation of enum values
> that could be
On 11/18/2015 03:09 PM, Eric Blake wrote:
> On 11/18/2015 10:08 AM, Markus Armbruster wrote:
>> Eric Blake writes:
>>
>>> In general, designing user interfaces that rely on case
>>> distinction is poor practice. Another benefit of enforcing
>>> a restriction against case-insensitive clashes is th
On 11/18/2015 10:08 AM, Markus Armbruster wrote:
> Eric Blake writes:
>
>> In general, designing user interfaces that rely on case
>> distinction is poor practice. Another benefit of enforcing
>> a restriction against case-insensitive clashes is that we
>> no longer have to worry about the situa
Eric Blake writes:
> In general, designing user interfaces that rely on case
> distinction is poor practice. Another benefit of enforcing
> a restriction against case-insensitive clashes is that we
> no longer have to worry about the situation of enum values
> that could be distinguished by case
In general, designing user interfaces that rely on case
distinction is poor practice. Another benefit of enforcing
a restriction against case-insensitive clashes is that we
no longer have to worry about the situation of enum values
that could be distinguished by case if mapped by c_name(),
but whi
