[Development] Naming convention for (scoped) enums

[Alex Blasche]

I updated the enum section:

https://wiki.qt.io/API_Design_Principles#Naming_Enum_Types_and_Values

--
Alex

________________________________________
From: Development <development-bounces+alexander.blasche=qt.io at qt-project.org> on behalf of Lars Knoll <lars.knoll at qt.io>
Sent: Tuesday, 22 May 2018 9:30:18 AM
To: Christian Kandeler
Cc: Qt development mailing list
Subject: Re: [Development] Naming convention for (scoped) enums



> On 17 May 2018, at 11:35, Christian Kandeler <christian.kandeler at qt.io> wrote:
>
> On Thu, 17 May 2018 08:14:15 +0000
> Alex Blasche <alexander.blasche at qt.io> wrote:
>
>> The naming conventions for enums state that each enum value name must repeat a part of the enum Type name (for details see https://wiki.qt.io/API_Design_Principles#Naming_Enum_Types_and_Values)
>>
>> In case of scoped enums this becomes a superfluous rule as the type has to be mentioned anyway. Does anybody object to modifying the above definition by adding an exception for scoped enums where you do not have to repeat a part of the enum type name?
>
> I would not have even assumed that the rule applies to scoped enums, but it can't hurt to write it down explicitly. Perhaps the section should be rewritten so that the unscoped enums are the special case rather than the other way around.

Agree. The default for new enums should be scoped enums.

Cheers,
Lars

_______________________________________________
Development mailing list
Development at qt-project.org
http://lists.qt-project.org/mailman/listinfo/development