Unscoped enums making a scope

[amber ivy]

This whole time I used unscoped enum values without a scope but I just realized that you can also access it through a scope. How exactly does this work? I know that in C the enum values just get injected to its surrounding scope so when I saw fha unscoped enums were just basically C enums I’m confused Why can it be accessed through a scope and just by itself ie.

enum MyEnum{
  VALUE
};

MyEnum x = VALUE; //works
MyEnum y = MyEnum::VALUE; //works

[native lynx]

When your question is answered use !solved or the button below to mark the question as resolved.

Remember to ask specific questions, provide necessary details, and reduce your question to its simplest form. For tips on how to ask a good question use !howto ask.

[bleak ivy]

It just is that way, they can be looked up with :: through their type or directly in the scope containing the enum definition

[paper prawn]

would ::VALUE also work ?

[bleak ivy]

that's just how they decided to design it to keep compatible with C but still make use of namespacing

[bleak ivy]

if this is in global namespace scope, yes

[amber ivy]

Do you know how that’s works? Like why it can be used with or without the name spacing? Just curious

[devout arch]

Because that's what it was like in C

C didn't have namespacing

[amber ivy]

So it’s injected into the enclosing scope like c?

Then why does it have a scope resolution or whatever it’s called lol

So it does it like c and cpp

[paper prawn]

what does "injected into enclosing scope" mean

[amber ivy]

In c since there are no namespaces if you do enum in the global namespace, the values are in the global scope. Ie, if you nest an enum in a struct, it doesn’t make a scope so it goes into the global scope.

I think that’s how it works??? I may or may not know what I’m saying

lol

[bleak ivy]

yes, it is, it behaves as if it was declared both in the enclosing scope and the enum's scope

[bleak ivy]

because that makes it consistent with how scopes work in other places in C++ without loosing C compatibility