I dropped by Power of Two Games blog after a long time. There were new posts. This tip is from one of those articles.

In my current project, we use the following naming rule for C++ enumerations.

    enum eSomeEnum
    {
        ESE_RED,
        ESE_GREEN,
        ESE_BLUE
    };

In this way to use the acronym of enum type name as a prefix, we found more duplicate prefixes than expected and it was hard to recognize the type from the prefix... So I have decided to use some other enum style in next projects and then I found this tip.

In a nutshell, it suggests the following.

namespace GameFlowType
{
    enum Enum
    {
        Invalid,
        Run,
        Exit,
        Restart,
        Restore,
    };
}

I think it's a very neat way.

namespace GameFlowType
{
    enum Enum
    {
        Invalid,
        Run,
        Exit,
        Restart,
        Restore,
    };
}

상당히 깔끔한 방식이라 생각합니다.

In C++, you can minimize repetitive tasks using macros. Messages registeration or registering  classes to the reflection system are such cases. In case that the registration cannot be done in one part of the code, we have to write duplicate informations more times. So DRY(Don't Repeat
Yourself) principle is broken and you are liable to many sync problems.

I found a useful tip at Visual C++ team blog. Suppose you want an enumeration and associated description strings as follows.

enum Animal { dog, cat, fish, bird };

wchar_t* AnimalDiscription[] = { L"dog", L"cat", L"fish", L"bird" };

If you have 'animal.inc' file as follows:

MYENUM(dog)

MYENUM(cat)

MYENUM(fish)

MYENUM(bird)

You can write following codes.

enum Animal {

#define MYENUM(e) _##e,

#include "animal.inc"

#undef MYENUM

};

 

wchar_t* AnimalDescription[] = {

#define MYENUM(e) L"_" L#e,

#include "animal.inc"

#undef MYENUM

};

 

What a neat trick!...