4.5 — Enumerated types

C++ allows programmers to create their own data types. Perhaps the simplest method for doing so is via an enumerated type. An enumerated type (also called an enumeration) is a data type where every possible value is defined as a symbolic constant (called an enumerator). Enumerations are declared via the enum keyword. Let’s look at an example:

Declaring an enumeration does not allocate any memory. When a variable of the enumerated type is defined (such as variable paint in the example above), memory is allocated for that variable at that time.

Note that each enumerator is separated by a comma, and the entire enumeration is ended with a semicolon.

Prior to C++11, a trailing comma after the last enumerator (e.g. after COLOR_MAGENTA) is not allowed (though many compilers accepted it anyway). However, starting with C++11, a trailing comma is allowed. Now that C++11 compilers are more prevalent, use of a trailing comma after the last element is generally considered acceptable.

Naming enums

Enum identifiers are often named starting with a capital letter, and the enumerators are often named using all caps. Because enumerators are placed into the same namespace as the enumeration, an enumerator name can’t be used in multiple enumerations within the same namespace:

Consequently, it’s common to prefix enumerators with a standard prefix like ANIMAL_ or COLOR_, both to prevent naming conflicts and for code documentation purposes.

Enumerator values

Each enumerator is automatically assigned an integer value based on its position in the enumeration list. By default, the first enumerator is assigned the integer value 0, and each subsequent enumerator has a value one greater than the previous enumerator:

The cout statement above prints the value 4.

It is possible to explicitly define the value of enumerator. These integer values can be positive or negative and can share the same value as other enumerators. Any non-defined enumerators are given a value one greater than the previous enumerator.

Note in this case, ANIMAL_HORSE and ANIMAL_GIRAFFE have been given the same value. When this happens, the enumerations become non-distinct -- essentially, ANIMAL_HORSE and ANIMAL_GIRAFFE are interchangeable. Although C++ allows it, assigning the same value to two enumerators in the same enumeration should generally be avoided.

Best practice: Don’t assign specific values to your enumerators.
Rule: Don’t assign the same value to two enumerators in the same enumeration unless there’s a very good reason.

Enum type evaluation and input/output

Because enumerated values evaluate to integers, they can be assigned to integer variables. This means they can also be output (as integers), since std::cout knows how to output integers.

This produces the result:


The compiler will not implicitly convert an integer to an enumerated value. The following will produce a compiler error:

However, you can force it to do so via a static_cast:

The compiler also will not let you input an enum using std::cin:

One workaround is to read in an integer, and use a static_cast to force the compiler to put an integer value into an enumerated type:

Each enumerated type is considered a distinct type. Consequently, trying to assign enumerators from one enum type to another enum type will cause a compile error:

As with constant variables, enumerated types show up in the debugger, making them more useful than #defined values in this regard.

Printing enumerators

As you saw above, trying to print an enumerated value using std::cout results in the integer value of the enumerator being printed. So how can you print the enumerator itself as text? One way to do so is to write a function and use an if statement:

Once you’ve learned to use switch statements, you’ll probably want to use those instead of a bunch of if/else statements, as it’s a little more readable.

Enum allocation and forward declaration

Enum types are considered part of the integer family of types, and it’s up to the compiler to determine how much memory to allocate for an enum variable. The C++ standard says the enum size needs to be large enough to represent all of the enumerator values. Most often, it will make enum variables the same size as a standard int.

Because the compiler needs to know how much memory to allocate for an enumeration, you cannot forward declare enum types. However, there is an easy workaround. Because defining an enumeration does not allocate any memory, if an enumeration is needed in multiple files, it is fine to define the enumeration in a header, and #include that header wherever needed.

What are enumerators useful for?

Enumerated types are incredibly useful for code documentation and readability purposes when you need to represent a specific, predefined set of states.

For example, functions often return integers to the caller to represent error codes when something went wrong inside the function. Typically, small negative numbers are used to represent different possible error codes. For example:

However, using magic numbers like this isn’t very descriptive. An alternative method would be through use of an enumerated type:

This is much easier to read and understand than using magic number return values. Furthermore, the caller can test the function’s return value against the appropriate enumerator, which is easier to understand than testing the return result for a specific integer value.

Enumerated types are best used when defining a set of related identifiers. For example, let’s say you were writing a game where the player can carry one item, but that item can be several different types. You could do this:

Or alternatively, if you were writing a function to sort a bunch of values:

Many languages use Enumerations to define booleans. A boolean is essentially just an enumeration with 2 enumerators: false and true! However, in C++, true and false are defined as keywords instead of enumerators.


1) Define an enumerated type to choose between the following monster types: orcs, goblins, trolls, ogres, and skeletons.

2) Declare a variable of the enumerated type you defined in question 1 and assign it the troll type.

3) True or false. Enumerators can be:
3a) assigned integer values
3b) not assigned a value
3c) explicitly assigned floating point values
3d) negative
3e) non-unique
3f) assigned the value of prior enumerators (eg. COLOR_MAGENTA = COLOR_RED)

Quiz answers

1) Show Solution

2) Show Solution

3) Show Solution

4.5a -- Enum classes
4.4b -- An introduction to std::string

91 comments to 4.5 — Enumerated types

  • tom mason

    When are the enumerators created? Can they be used independently of the enum-type variable? It appears that they are declared as -static const int-

    • Enums are handled at compile time, and they are generally treated as a const int. There is no such thing as a static type, so the static keyword is not applicable. The scope of enum type declarations is the same as normal variables: Enums declared outside of a class or function are treated as global, those inside a block are scoped to that block, and those in a class are considered part of that class.

      For example:

      Enum values can be used independently of the enum-type variable, as they are essentially treated as integers. For example, the following is valid:

      Note that in the specification for the next version of C++ (C++0x), there will be a new type of enum (called a strongly typed enum) that will be treated as a unique type. These strongly typed enums will not be implicitly convertable to integers.

      • Sasan

        Can we define all of our Enums in a separate file (.cpp) and forward declaration them in a Header file and then include that? I tried to do that but compiler gave me error on this (in header file):

        enum Color;

        • Alex

          No, you can’t forward declare enums.

          However, there’s no need. Because defining an enum doesn’t use any memory, it’s fine to define your enum types in a header and #include that header wherever you need access to the enum type.

  • Ben

    Not sure I understand its interest. If you’re trying to get a more understandable error message for example, I don’t see much difference as it will still print an integer and not “ERROR_OPENING_FILE”. Same idea with a list of names, etc…
    Is there a way to print the name of the enum and not its integer value?


    • Unfortunately, there’s no easy way to print the name of the enum. The main benefits of using enums are:
      1) Code readability is enhanced, since enums are descriptions and numbers could mean anything
      2) If you ever want to change an enum’s corresponding integer value, you only have to do so in one place, whereas if you use integers everywhere, you might have to change multiple values.

      Enums are often used in conjunction with functions, either as parameters or return values to denote a particular mode or state.

  • Rousseaux

    i will have to reread this lesson later. But i’m with Ben as far as seeing more use in the name of the enum type being printed in the stead of the actual integer. i tried to find a way to cout the name by feeding the integer value but that skill is beyond my scope so far. Once again you’ve fueled new ‘what if’s’ Alex. Well done.

    • If I need the names of a set of enums for something, I’ll usually write a function that takes the enum name to be printed and return a string version of the enum. Something like this:

  • Kinten

    I dont see the reason for usin enums instead of macros, I mean, if you use the enum it is necesary to initiate at least one instance of it, while the macros (#define) replace everyting right away without the memory cost.
    Isn’t this a better solution?

    • Enums and #defines have the same memory requirements. Enum definitions take up no additional memory space because they are just definitions. A good compiler should replace any enum with its integer equivalent at compile time, just like #defines are replaced by the preprocessor.

      Enums are always a better choice than #define when you have a set of options to pick from because the syntax checking will exclude you from picking something not part of the enum set. Plus they’re more readable, and debuggers can resolve their values (whereas debuggers generally can not resolve the values of #defines).

  • Sim

    Is there any other situation, in which enumerators are needed typically? Cause as of now I don’t see any difference between doing this:

    and this:

    Obviously these are constants, thus they cannot be changed during runtime. However, if this is the only typical way of using enumerator types, then I don’t see why you wouldn’t just pre-define them using the preprocessor.

    • Alex

      As I noted above, Enums are always a better choice than #define when you have a set of options to pick from because the syntax checking will exclude you from picking something not part of the enum set. Plus they’re more readable, and debuggers can resolve their values (whereas debuggers generally can not resolve the values of #defines).

  • Shai

    Great work, Alex.
    Your site is better than any C++ book I know of.

  • John

    I hope that is all in code !

    When I run this, I get the exception in the PrintBodyPartStatus(), which prints 0 0.
    And the check above the exception, is expecting a 0, 0.
    What am I missing? Am I doing this wrong? It seems like a viable way to use Enums, as I’ve been using consts for EVERYTHING until I had a look at some open source game Enums.

    I’m currently working on this, so don’t think I’m commenting to expect you to do it for me (which would be nice, I admit)
    But I really didnt’t see the point in typing out

    where in a few less line I coult just type in

    Thanks in advance

    changing the check from && to || make it work. I’ve always wondered why OR checks work properly and AND checks don’t. (Maybe I’ve been doing those all wrong too, but I’ve always had the problem, even on simple checks.

    even compound if’s don’t work very often


    • Luiwtf

      should be:

      note the 2 =’s, instead of one 🙂

      the reason it works with || is because the second half comes up true as you have the == correct, as it is the first part is irrelevant.

      edit - meh, just noticed it’s a month old :D, i suck at remembering dates :p.

  • SWEngineer

    Simple well explained tutorial. Thanks.

  • newUser

    If I had not read the comments I would have never noticed enum uses commas! May I suggest having it written in the tutorial too so it draws more attention to it?

  • kalvin

    Enumerations are a little confusing for me. I would better understand them if i had a practical use for them.. I know that no arithmetic operations are allowed on enum, and that since enums are an ordered set of values, you can use relational operators, and loops. this being said I guess I can see how using enum to make your program more readable might be benificial. But to really incorperate enums into your program you will have to input and output enums indirectly as you can not directly output or input enumeration data types.. So for now , i think you have to choose whether to make your program more readable with more work using enumerations, or not and save the extra programming.. Idk maybe as i learn and play with this more i will find its practicality

  • KanedaSyndrome

    This was an area that I haven’t worked with before, so it was fun to get into.

    My contribution:


    enum monsters

    declaraction and assignment

    monsters newMonster = TROLL;


    cout << endl << newMonster; //outputs the value 2


  • Jannat

    Hi. I found these enumerated types really interesting. So I tried to make this program.
    I keep on getting the following error.

    error: no match for ‘operator>>’ in ‘std::cin >> eColour’|

    using namespace std;
    int main ()
    { //program to input a colour and output the lucky number. lol
    enum colour
    red = 1,
    blue = 2,
    green = 3,
    colour eColour = red;
    cout<<"Choose a colour "<>eColour ;
    cout <<" Your lucky number is "<<eColour<<endl;
    return 0;

    What's wrong with cin ? can these enumerated data types not be input?

    • Alex

      No, you can’t use cin to input enumerated types. If you want to do this, have the user input an integer and then use a static_cast to convert it to your enumType.

  • dice3000

    Awesome tutorial. I actually learned something really useful

  • JesseZhuang

    Is non-unique enumerators useful in any case in practice?

  • Subhan

    Can’t I set enumerated values to be greater than int values? Example

    • Alex

      The C++ standard says: “It is implementation-defined which integral type is used as the underlying type for an enumeration except that the underlying type shall not be larger than int unless the value of an enumerator cannot fit in an int or unsigned int”.

      So in theory, if you have an enumerated value that is larger than an int, the compiler should pick a larger integral type. Visual Studio 2010 errors on your example because it doesn’t have any integral types larger than int. Compilers compliant with C++11 should allow this though, as they could pick a long long integral type.

  • Joseph

    Should the last enumerator variable have a comma after it?
    Wouldn’t the compiler expect another variable to follow and give an error? Mine doesn’t so I don’t know if this is okay or not.

    enum MonsterType

    • Alex

      This is a surprisingly complicated answer.

      C++ didn’t allow the last enumerator to have a comma until C++11, where they started allowing it.
      C didn’t allow the last enumerator to have a comma until C99.

      So it really depends on what set of standards your compiler adheres to. Any C++11 compatible compiler should allow it. Any pre-C++11 compiler may or may not allow it for C99 compatibility purposes. It sounds like yours does allow it.

  • Jeremy

    I’m having a heck of a time trying to figure out how to forward declare enumerated classes/structs (same thing, I know). I know you haven’t touched on scoped and unscoped enums here yet, but you probably will in the future. I think they’re cool and all, but I can’t figure out how to make a forward declaration work for them. It seems easier to just stuff the whole definition in a header file and include it to avoid the headache, but surely forward declarations for enums (and structs for that matter) exist for a reason?

  • jianping

    in the example:

    what if there are two enumerators with assigned value 5?

    • Alex

      It still works. Enumerators aren’t guaranteed to be distinct, so two enumerators with the same value are essentially interchangeable.

      Although it doesn’t make any sense:

      This prints “Color is equal to GREEN” because we assigned the same value to the enumerators BLUE and GREEN.

      In short, the takeaway is that generally you shouldn’t assign the same value to two enumerators in the same enumeration.

      • ColorMan

        What if:

        It works for me! Althought Color enumeration has only 8 Colors!
        Great Tuts!
        P.S: You should add a union section after this one. 😉

        • Alex

          Yup, you can cast an integer to an enumeration value that doesn’t have an associated enumerator.

          I’ll think about adding a lesson on unions. They’re not used very often, but they can be interesting in some cases.

  • Jana

    Hi Alex,

    In your last comment, line 12 of the code: Color color = BLUE; What do ‘Color’ and ‘color’ refer to?
    I expect that ‘Color’ is the enum identifier, but not sure about the other one.

    Also, why do you sometimes use eColor (e.g. in Enum type evaluation and input/output)?

    Thanks a lot.


    • Alex

      This declares a variable named color of type Color (which is an enumeration defined previously), and then sets the value of color to BLUE.

      When this lesson was first written, I used the prefix “e” on all enumerator variables. Since then, I’ve moved away from that naming convention, but I missed one instance. It’s updated now.

  • Eric

    I’m reading your tutorial as a precursor to a C++ video game development tutorial, so obviously this example intrigued me. But I don’t understand how it is useful.  So you’ve a got string ("torch"), you have an enum called itemType with value (ITEMTYPE_CARRYABLE), but how are those in anyway related?  How could you use those in context?  I mean, if you were trying to "use" the torch and decide what to do with it, how would your function know that "torch" was a "ITEMTYPE_CARRYABLE"?  I’m really frustrated because I feel like this example went right over my head, but it seems extremely useful.  Would really love some clarification!

    • Alex

      The short answer is that the example I provided wasn’t very good. I’ve updated the example to one that I think is more straightforward. Check it out and let me know if that answers your question.

      It is common to use enums to define “categories” of things (like I did in the original example you quoted). These can be used in many different ways. For example, if you had an array of all the items in your game, it might be useful to assign a type to each item so that you’d know how to handle them (e.g. weapons get held, armor gets worn, consumables get used).

      Alternatively, each of your items could have a type (as defined in the example you quoted) and a subtype (that specifies whether the weapon is a sword or a dagger or a bow, or the carryable is a torch or a shield), and use them in pairs.

  • Todd


    "An enumerated type (also called an enumeration is a data type…" (insert an end parentheses after "enumeration")

  • Anuj

    In the line number
    11.std::string getItemName(ItemType itemType)…"getItemName is a keyword or anything can be written with get??

  • techsavvy....aye

    How to use switch statements for the program

    • Alex

      Switch statements for enums are covered in lesson 5.3 -- Switch statements.

    • saeid

  • techsavvy....aye

    How can I output in the above program I tried many things but couldn’t. It must be some small mistake could you tell me how to do it.

    • Alex

      I don’t understand what problem you are having. Did you try this?

  • techsavvy....aye

    Oh!! got it I was putting a small ‘c’ for ‘color’ instead of ‘Color’.
    got it, thanks!

  • techsavvy....aye

    In the first answer of quiz I think the last enumeration shouldn’t have a ‘,’.

  • Vishnu

    I think there are ; missing from the game(sword,torch etc) example given above after the return statements defined under "string getItemName(…..)"  .

    Please correct me if I am wrong. 🙂

  • Night Owl

    Hello Alex,

    On the quiz part of this section, what do you mean by " enumerators can be non-unique"?

    I know many people have said this, but thanks for all you hard work on the lessons and this website.

    • Alex

      I updated the wording to be more clear:

      “These integer values can be positive or negative and can share the same value as other enumerators”

      Basically, two different enumerators can resolve to the same value.

  • begginner

    using namespace std;
    enum Monster{
    function(Monster monster){
            cout<<"you choose a RAT!";
            cout<<"you choose a LORD!";
            cout<<"you choose a DRAGON!";
                cout<<"you choose a BULL!";
                cout<<"you choose a DOG!";
    why i am getting extra valur after my enum type.

  • Jim

    Making your own data type using enum Color and auto. assigning COLOR_BLACK a value 0 all seems pretty simple for just 7 color.

    What’s going to be hard is defining all the colors to make up a pallet (2^8)256 or more and how and what you need to do to use them.

    So can I assume some of this has already been done for us in C++? Or maybe we can find this in some library out there?

    • Alex

      Enums are useful when you have well defined set of things that have discrete names.

      For something like a palette of 256 colors, I probably wouldn’t use an enum. Creating names for all 256 colors and setting up huge switches to handle them doesn’t seem efficient or readable. At that point, you’re probably better of just passing an RGB color value.

  • Jim

    It seems pretty redundant to name an enum Color and then use COLOR_RED as one of the enumerator names. Did you do it that way for a specific reason?

    Why not just use RED like in the first example you showed? Would it be alright to use one or any of these C_RED, COL_RED, CLR_RED instead. I realize you’d have to be consistent with all the enumerators. Differentiating between all of these Color, color, COLOR is real confusing.

    A bit later you used this cast, Color color = static_cast<Color>(inputColor).  However you used color in all lower case letters, how does this one work?

    Can you explain this a little better?

    • Alex

      > It seems pretty redundant to name an enum Color and then use COLOR_RED as one of the enumerator names. Did you do it that way for a specific reason?

      Yes. With normal enums, the enum name isn’t used to scope the enumerator. So let’s say you had two enumerations:

      Color’s BLUE enumerator will have a naming conflict with Mood’s BLUE enumerator. Adding a prefix to the enumerator help avoid naming conflicts and also serves as a reminder of which enumeration the enumerator is from. You can use any prefix you like.

      > Color color = static_cast(inputColor). However you used color in all lower case letters, how does this one work?

      In this line, we’re declaring a variable named color of type Color (no different than how int x declares a variable named x of type int). We’re initializing variable color with the inputColor, converted from an int into a Color.

  • Sharaf

    hey i didn’t understand the code

    here why you have used ItemType and itemtype i didn’t understand use of that..
    even how you defined this string i didn’t understand
    std::string(ItemType itemType)

    • Alex

      ItemType is the enumerated type that I’ve defined at the top of the code. itemType (lower case i) is the name of a variable I’m defining. ITEMTYPE_TORCH is the enumerated value that I’m initializing variable itemType with.

      It’s akin to this: int x. int is the type, x is the variable name. In this case, instead of int, we have ItemType. Instead of x, we have itemType.

      I’m not sure what you mean by “std::string(ItemType itemType)”, as that doesn’t occur in the code anywhere.

    • Lyle

      This defines a function named getItemName which returns a string when it returns instead of say, an int which most examples in the tutorial use.

      The argument passed when you call it is one of the Item_Type enum items.
      When the function is called and returns, this example - it will leave a string of "Torch" for cout to display.

  • Elpidius

    Hey Alex, could you please clarify (and perhaps reword) this:

    "The C++ standard says the enum size needs to be large enough to represent all of the enumerator values. Most often, it will make enum variables the same size as a standard int."

    So in regards to the enum variable size, are you saying the enum variable needs to be large enough to hold the largest possible integer value of an enumerator?

    For example:

    So in this hypothetical case the largest possible value is 258 (takes up 259 values), which cannot fit inside an 8-bit variable (it can only hold 256 values), hence we need to allocate a 16-bit piece of memory for this enum variable.

    Is my understanding of this correct?

  • Shiva

    A note on printing enumerators:

    I see a lot of people asking in their comments for a proper way to print enumerator names instead of their integer values. As Alex says there’s no direct way to do this, his own solution being to use a function, which is nice. But I found an easier solution which is to use an array of strings to store the enumerator names, and use the enums as array indices. e.g.

    This is the method I used to print the monster’s type in solving Chapter 4’s Comprehensive Quiz, and it works as expected. No one seems to have mentioned it so far, including Alex, but may be that’s because we haven’t covered arrays yet. It’s pretty obvious to anyone who’s familiar with arrays, just thought I’d share it anyway.

    Is there any downside to the approach? Your thoughts, Alex?

    Keep coding. ~Shiva 🙂

    • Shiva

          Put a #include <strings> in there before the first line. I missed it. 🙂

    • Alex

      Yes, I didn’t mention this method because we haven’t covered arrays yet. This certainly works. The primary advantage I can think of to this method is that it’s likely to be a little more performant (since an array lookup is probably more performant than a function call). But I’d still recommend using a function for a few reasons:

      * With a function, the mapping between the enumerators and names is made explicit. With an array, you’re implicitly relying on the numeric ordering, which is more prone to error.
      * A switch statement gracefully handles a default case, which you can use for error handling in case you define a new enumerator and forget to assign a string to it. An array doesn’t have a mechanism for catching missing enumerators.
      * C++ won’t give you a warning if you have less array initializers than the size of the array, so it’s easy to accidentally miss an enumerator and have everything off by one.

      • Shiva

        Good points. Another drawback that occurred to me is that this won’t work if the enumerators are explicitly assigned non-continous integer values, because array elements are always referred by continuous indices starting from zero. The syntax is also less readable, especially if one is using enum class instead of normal enums. Still it could be useful for someone who’s actually looking for something like it. 🙂

        So anyone should use this method only in simple, straight-forward cases where performance is a primary factor, a function in all other cases.

        Thanks for the advice, Alex. 🙂

        • Alex

          Good point about non-contiguous enums (though those are uncommon).

          Yes, the key takeaway is using a function is a better practice unless you really need the performance (and it may not even be more performant if your compiler inlines the function). A good rule of thumb is not to optimize too early -- write safe code first, and then if you need more performance, you can figure out how to optimize. Otherwise you’ll likely end up spending time optimizing things that don’t matter, for little benefit.

          • Shiva

            Right on all accounts. Makes sense. Agreed.

            The real gem of this website over other C++ learning resources is very much this platform to ask questions and get the practical methodology and insights of a pro in return. Thanks a lot Alex. 🙂

  • Jim

    Is the first part of this lesson (shown below) worded incorrectly?  The first sentence alone does not make any sense.  Is enum a data type or just a keyword used to make a new data type of your own? It doesn’t make sense to use a data type to make another data type.  e.g. Enumerator (enum) a data type and COLOR a data type?
    Is COLOR the symbolic constant? What are RED,GREEN,BLUE? So this is confusing.

    It might make sense if type enum was making an array COLOR and all the colors were elements of the array. Can you please clarify this?

    "Do you need to use C++ allows programmers to create their own data types. Perhaps the simplest method for doing so is via an enumerated type. An enumerated type (also called an enumeration) is a data type where every possible value is defined as a symbolic constant (called an enumerator). Enumerations are declared via the enum keyword. Let’s look at an example:"

    • Alex

      I’m not sure where the “Do you need to use” came from. I don’t see that.

      enum is a keyword that allows you to create your own custom enumerated data types.

  • Darren

    This code will compile without error from c++11 on-wards,

    The enums are said to be strongly typed by following them with the class keyword. However, in order to gain access to the items you have to scope them to their enum names, which makes sense as the items RED and GREEN would be ambiguous otherwise.

  • Shekhar

    Hi Alex, I am not clear about this statement: "Because the compiler needs to know how much memory to allocate for an enumeration, you cannot forward declare enum types."
    My doubts are:
    1) First of all, is memory allocated at compile time or at run time ?
    2) Second, so when we forward declare a variable, does the compiler set aside memory (or compile the instruction to set aside memory) for it ?
    3) Third, for function forward declarations, does the compiler set aside memory (or compile the instruction to set aside memory) for the function. Since for a function the compiler knows the number of variables from the function forward declaration it’s not a problem. But for an enum forward declaration, it wouldn’t know the number of enumerators within the enum type, is that the reason we cannot forward declare enum types.

    Please let me know your thoughts


    • Alex

      1) Memory is always allocated at run time, but it can be allocated from different regions depending on how the variable is declared.
      2) No, a variable forward declaration just tells the compiler that a variable exists. Only instantiating a variable actually causes memory to be allocated.
      3) Functions are stored in a special region of memory (after all, the code has to live somewhere). Function forward declarations also just tell the compiler that a function exists.

      You’ve hit the nail on the head in point 3 -- the compiler is free to determine how many bytes to allocate to an enum variable -- and to do that, it needs to know how many enumerators are in the enum. It can’t determine that from a forward declaration. The good news is that it hardly matters -- if you put your enumerations in a header file, you can just include that header file wherever you like and have access to the enumerated type. The enumerated type declaration doesn’t take any memory -- only instantiated enum variables do.

  • Sanja

    What do you think under #defined values?

  • reznov

    So for the sake of trial I attempted to declare my enum MonsterType in a headerfile and #included the header file in the file I wanted to assign it a value.

    I expected this to work, since the #include statement should’ve been replaced with the content of the header file, but it didn’t. My compiler didn’t seem to know what I was talking about when I called my enum type and it’s values. Is this because it doesn’t allocate memory until assigned? Or is there some other conflict going on here I don’t know about yet?

    • Alex

      No, this should have worked. It’s common to put enums in headers and then #include them. Something else must be going wrong. If you copy the enum from the header into the code file at the point where you did the #include, does it work?

      • reznov

        Yes te enum did work properly when implemented in the code, this is why I started blaming the #include. That was a correct assumption however, as I just reviewed my code after a night of sleep and knowing it should work. My error was using #define ‘monster_type.h’ where the compiler thinks (I don’t know a file called string::monster_type.h), instead of "monster_type.h".

        Eventually was gonna make that mistake one day, might as well be now. Anyway I’m glad the code works, thanks 🙂

  • Coder

    Hi Alex! Thank you for the tutorial!

    I have a little question concerning quiz 3c:

    In question 3c we were asked, if enumerators can be explicitly assigned floating point values, and answer was false. However, I made a small program where I used static_cast-operator to cast a floating point value to an integer and it worked:

    Did I understood the question incorrectly? Thanks.

  • Sam

    Hi! Should use

    instead of

    nowadays, to not polute the namespace.

    • Alex

      Hi. That’s a bit of an over-generalization. Enums are still a fine choice if you’re using them inside a namespace or class (in that case, the extra namespacing provided by enum classes probably isn’t needed). If you’re defining them in the global scope, then enum classes are probably better. See the next lesson for more information on enum classes.

      • Sam

        Wow, that’s a fast answer! Thank You for the reply, You’re right, that’s more specific. Didn’t notice the following topic is about exactly that. Shoulda paid attention.

  • kleinstein

    My solution for the MonsterType:

Leave a Comment

Put C++ code inside [code][/code] tags to use the syntax highlighter