Sepples "scoped/class enum" Retardation

https://smartbear.com/blog/develop/closer-to-perfection-get-to-know-c11-scoped-and-ba/
https://en.cppreference.com/w/cpp/language/enum
So uh, basically instead of BronzeColor
we use Color::Bronze and when we have to assign to int we use static_cast(while C doesn't need anything and typing is easier).

The underlying problem is the usage of code-polluting paamayim nekudotayim instead of the ..

C: enum bepis { sweet, sour };
void f(enum anus, ...);
this is valid: f(sour);
And if you also have enum candy { sweet }; you will get an error
Thanks C!

>>3
The solution was right in the article
CategoryNameEnumValue, no need to use same
identifier and being retarded.

Artificial problem. When do you actually use same identifier for two enums?

>>4
f(sour)

>>6
Do you think you're clever? Fuck all the way off.

This is an extremely useful feature that prevents bugs.

it's too much typing

You mean you don't have autocomplete? In 2019?

C:
enum Color {BronzeColor,SilverColor,GoldColor};

enum Bullion{SilverBullion,GoldBullion,PlatinumBullion};
Color col1=BronzeColor;
if ((col2==SilverColor) || (col2==GoldColor))
int carcolor=SilverColor;

C++:
enum class Color //C++11 scoped enum
{Bronze,Silver,Gold};

enum struct Bullion //C++11 scoped enum
{Silver, Gold,Platinum };
Color col1=Color::Bronze;
if ((col2==Color::Silver) || (col2==Color::Gold))
int carcolor=static_cast<int>(Color::Silver);

Fuck unicode

>>7
More so than you, yes.