S.4.x — Chapter 4 comprehensive quiz

Quick review

We covered a lot of material in this chapter. Good job, you’re doing great!

A block of statements (aka. a compound statement) is treated by the compiler as if it were a single statement. These are placed between curly brackets ({ and }) and used pretty much everywhere.

Local variables are variables defined within a function. They are created at the point of variable definition, and destroyed when the block they are declared in is exited. They can only be accessed inside the block in which they are declared.

Global variables are variables defined outside of a function. They are created when the program starts, and are destroyed when it ends. They can be used anywhere in the program. Non-const global variables should generally be avoided because they are evil.

The static keyword can be used to give a global variable internal linkage, so it can only be used in the file in which it is declared. It can also be used to give a local variable static duration, which means the local variable retains its value, even after it goes out of scope.

Namespaces are an area in which all names are guaranteed to be unique. Use of namespace is a great way to avoid naming collisions. Avoid use of “using statements” outside of functions.

Implicit type conversion happens when one type is converted into another type without using a cast. Explicit type conversion happens when one type is converted to another using a cast. In some cases, this is totally safe, and in others, data may be lost. Avoid C-style casts and use static_cast instead.

std::string offers an easy way to deal with text strings. Strings are always placed between double quotes.

Enumerated types let us define our own type where all of the possible values are enumerated. These are great for categorizing things. Enum classes work like enums but offer more type safety, and should be used instead of standard enums if your compiler is C++11 capable.

Typedefs allow us to create an alias for a type’s name. Fixed width integers are implemented using typedefs. Typedefs are useful for giving simple names to complicated types.

And finally, structs offer us a way to group related variables into a single structure and access them using the member selection operator (.). Object-oriented programming builds heavily on top of these, so if you learn one thing from this chapter, make sure it’s this one.

Quiz time!


1) In designing a game, we decide we want to have monsters, because everyone likes fighting monsters. Declare a struct that represents your monster. The monster should have a type that can be one of the following: an ogre, a dragon, an orc, a giant spider, or a slime. If you’re using C++11, use an enum class for this. If you’re using an older compiler, use an enumeration for this.

Each individual monster should also have a name (use a std::string), as well as an amount of health that represents how much damage they can take before they die. Write a function named printMonster() that prints out all of the struct’s members. Instantiate an ogre and a slime, initialize them using an initializer list, and pass them to printMonster().

Your program should produce the following output:

This Ogre is named Torg and has 145 health.
This Slime is named Blurp and has 23 health.

C++11 solution: Show Solution

non-C++11 solution: Show Solution

5.1 -- Control flow introduction
S.4.8 -- The auto keyword

247 comments to S.4.x — Chapter 4 comprehensive quiz

  • Tushar

    I did a bit differently. It shows me this error

    Compilation failed due to the following error(s).
    main.cpp: In function ‘int main()’:
    main.cpp:18:40: error: invalid conversion from ‘const char*’ to ‘int’ [-fpermissive]
         monsters ogre ={{"Torg",145},"ogre"};

    • nascardriver

      `monsters` has 3 members, but the initializer list

      has only 2 elements (One if which is another initializer list). `{ "Torg", 145 }` is used to initialize `name_of_monster`, then an attempt is made to initialize `health_to_die` with "ogre", but that doesn't work.
      You need to dissolve the inner initializer list.

      • Tushar

        I have used a nested structure following this code in the tutorial. But i can't understand why it didnt work?

        • nascardriver

          Each value in the initializers list corresponds to a value in the struct.

          The inner initializer list is used to initialize the object `CEO`. In your code, you don't have a sub-object like that.

          When you remove the inner initializer list, the members match up.

          • Tushar

            • nascardriver

              Because it's in the place where `name_of_monster` is. The first value in the initializer list is what will be used to initialize `name_of_monster`.

              An `std::string` can be created with a string and an int, the int specifies how many characters to copy.

              That's what's happening in your code with `{ "Torg", 145 }`.

  • Gacrux

    My code was 99% spot on, but instead

    I made

    which causes the following error

    main.cpp||In function 'void printMonster(MonsterData)':|
    main.cpp|32|error: could not convert 'monster.MonsterData::type' from 'monsterType' to 'MonsterData'|

    Why we need to send to printMonster the whole struct instead of just one of the elements (monster.type) like the others and

  • derek

    I was testing my code and it seems like using "enum class" breaks the program whereas "enum" works fine.

  • Avijit Pandey

    Here is a modified version of the solution to the question.
    I modified the program so that we can take the input from the user for all the three parameters and it works.
    Now my question is, is there a way to create a single function for taking in the input for all the three parameters?

    • - Don't use `using namespace`.
      - Line 23+, 64+ Should be `else if`.
      - Line 21+: You're mapping the values to enumerators with the same values. Use a `static_cast` instead.
      - Line 87, 88: Execution order of the arguments is undefined. If you don't care, that's fine. If you want the functions to be called in a certain order, call them before you construct a monster.

      > is there a way to create a single function for taking in the input for all the three parameters?
      You're pretty close already.

      • Avijit Pandey

        Thanks for the quick response, and the tips.
        I don't understand how the execution order of the arguments is undefined in line 87 and 88.
        When I do something like

        the values of the parameters of the struct get assigned in that order.
        So, don't the three functions(used as arguments here) get called in that particular order?

        • > When I do something like [...]
          Yes, the members are initialized in that order.

          > So, don't the three functions(used as arguments here) get called in that particular order?
          No. They're evaluated in an arbitrary order and their return values are stored in temporaries. Those temporaries are then passed to the constructor. The members are still initialized
          type -> name -> health
          But the function call order is undefined.

      • Mike

        What do you mean by this? I'm doing something similar with my code, but I have no idea what you mean with this statement:

        - Line 21+: You're mapping the values to enumerators with the same values. Use a `static_cast` instead.

        It's working as is, so I'm not sure what "values" you're referring to that needs to be converted with a static-cast or to what type. Is "mapping" the same as "returning" in this context? And if so, I don't understand what other type they should be returned as other than their inherit type as currently defined.

        • Mapping means turning the values of set A into values of set B. Then, when you want to know which value in B a value from A corresponds to, you just look at the map.
          In this case, this is the map

          Recall that enumerators have integral values. They are numbered in the order of their declaration, starting at 0.

          You're using a switch-statement to turn the numbers into `Type`s. But that's not necessary, because the numbers you're using as an input are exactly the same as the enumerator's values. The entire switch-statement can be replaced with

          • Mike

            Thank you for the reply, it was comprehensive and extremely helpful to me. Without the extra details you provided, I would still be scratching my head as I don't think we've covered mapping or the idea of it in programming.

            I do have a follow up question regarding the if statement you provided. I noticed yours was missing the 2nd left parenthesis after the &&, but even when I added it, it still said I was missing a parenthesis or that one was expected. To finally get it to work, I had to add four right-sided parentheses to the end of the if statement as shown below. That doesn't seem right for this statement. If it is, please explain why, because I see as this:

            Each condition has one set of parentheses, plus one extra set for each expression in each cast. So each condition should have a total of 4 parentheses, totaling 8 for both. Yet it's requiring 12. What am I missing?

  • Sam

    Here is my solution! I appreciate any feedback, so please feel free to leave any :)

    • Man you were busy.
      Return, initialization, naming and indention from my previous comments apply here too.

      - Limit your lines to 80 characters in length for better readability.
      - `getMonsterType` and `getWeaponType` should return an `std::string_view`. This isn't covered on learncpp. Returning an `std::string` will construct a new string on every call, that's slow.

      • Sam

        Once again, thank you so much for your feedback! I updated the code, but the online compiler I am using doesn't appear to be compatible with "std::string_view". I also attempted to use it by including the <string> header, but that didn't seem to work as well. Anyways, here's the code!

        • `std::string_view` is declared in <string_view> and was added in C++17.
          Line 71, 75, 79, 83 should be indented, because they're an extension of the previous line respectively.
          You're starting to use abbreviations ("m", "w"). They're still readable, because their use is close to their declaration, but don't let this get out of hand. Time saved writing is time wasted reading.

  • Alexander S.

    Trying to make a loot box open simulation thing but when I set the amount and if the object will be given it doesn't recognize that it was changed when I run it outside the function determineLootType()

    • - Initialize your variables with brace initializers.
      - Use std::rand instead of its global-namespaced counterpart.
      - If your program prints anything, the last thing it prints should be a line feed ('\n').
      - You're using the same name style for variables, functions, and types. This will lead to confusion.
      - `main`: Missing return-statement.

      Whenever you encounter a problem, please also post code that produces the problem, the output, and the expected output.
      I'm guessing you mean this

      By default, variables are copied when you pass them to functions. `determineLootType` modifies a copy, which doesn't affect the original. You can use a reference to pass the original object

      References are covered later.

      • Alexander S.

        I never can seem to remember return 0 in main lmao. A lot of the console printing was testing stuff I was using to see if I could get the right values and stuff that I didnt remove before sharing.

        I will try to do better with naming. Also sorry for not being clear on the code.

        I have done a bit with refrences, used them in the past as I came to a sudden revaluation that they would fix the error in that program. Haven't touched them since then though so I kinds forgot they allow you to do things like that.

        Thank you for your help!

  • Alexander S.

    Any errors, I assume some might be with the Struct.

    • Hi!

      - Line 3: `using std::string;`.
      - You don't need to break after returning. A return stops everything.

      • Alexander S.

        Good to know, contemplated using std::string but I just did the using string one as a way to kind of reinforce the format of the typedef stuff.

        The return one was also one I thought about but I did it anyways just in case it breaks my switch statement.


  • learning

    Improvement suggestions?

    Thanks in advance.

  • p1n

    What about this solution,instead of writing 2 functions?

  • I did my best to structure this carefully and follow best practices. I don't like jumping ahead of the lessons, but I really wanted a random number here. It seemed appropriate to nest my enum class inside of my struct, but I see that the example didn't do this. Monster::Type::Foo is getting pretty lengthy, would you recommend using typedef here? Appreciate you taking a look at this!

    EDIT: Presently Ogre is the default option, in-case the user makes an invalid choice.

    • - Use std::rand instead of its global-namespaced counterpart.
      - Use std::srand instead of its global-namespaced counterpart.
      - Use std::time instead of its global-namespaced counterpart.
      - Don't use `std::system`, it won't work on other platforms.
      - `std::time` wants a pointer, pass `nullptr`.
      - `std::srand` wants an unsigned int, add a cast. You should've gotten a compiler warning.
      - Line 59+: Should be `else if`.
      - Don't mix '\n' and `std::endl` unless you have a reason to do so.
      - Inconsistent formatting. Use your editor's auto-formatting feature.
      - Use `<ctime>` instead of `<time.h>`. Most of the `*.h` headers are C compatibility headers. The `<c*>` headers declare their contents the `std` namespace.
      - Inconsistent variable name style ("Health" vs "name"). Pick a convention, stick to it.

      > nest my enum class inside of my struct
      If you do that, you can use a regular `enum`. Name collisions are mostly prevented by the encapsulating struct. If you use a regular `enum`, you can access the enumerators via

      • Hey, thanks! I'm posting the updated code below. I didn't know there was an auto-formatting feature, that's very helpful. I believe that I implemented every correction except for one: I kept the std::system("CLS"); because I wanted to ask you whether or not there's an alternative. If there isn't, I will happily remove it. Also one more question, is using 'else if' as opposed to 'if' simply a matter of adhering to best practice formatting conventions, or is there something happening there?

        Appreciate your hard work very much, thanks again!

        • - Line 80: Use std::time instead of its global-namespaced counterpart.
          - Line 74: Don't mix '\n' and `std::endl` unless you have a reason to do so.
          - Line 31+: Should be `else if`.

          > I kept the std::system("CLS"); because I wanted to ask you whether or not there's an alternative
          There is no universal way of clearing the terminal/console. The terminal/console is a program in itself, how it's controlled is up to the developer of the terminal/console.

          > is using 'else if' as opposed to 'if' simply a matter of adhering to best practice formatting conventions, or is there something happening there?
          In this case, there's no difference, because each if's body returns. In general, if one condition excludes the next, use `else if`.

  • Richard Flores

    Instead of
    > if (monster.type == MonsterType::OGRE)
    Can we use
    > if (monster.type == 0)
    Since enum values evaluate to integer anyway?

    If yes, during our declaration of struct Monster, can we technically do
    > int type
    instead of
    > MonsterType type?

    • > Can we use
      If `MonsterType` is `enum class`, no. If it's a regular `enum`, yes.

      > during our declaration of struct Monster, can we technically do

      If you do so, you'll have no idea which number is supposed to mean what. Enums are there to prevent exactly this.

  • My program keep exit with code 2, even when I use the exact code from solution, how do I fix this?
    #include <iostream>
    #include <string>

    // Quiz
    // Define our different monster types as enum

    enum class MonsterType {

    // Our monster struct represents a single monster

    struct Monster {
        MonsterType type;
        std::string name;
        int health;

    Monster monster0(MonsterType tr) {

    // Return the name of the monster's type as a string
    // Since this could be used elsewhere, it's better to make this its own function

    std::string getMonsterTypestring(Monster monster) {
        if (monster.type == MonsterType::DRAGON) {
            return std::string("Dragon");
        if (monster.type == MonsterType::GIANT_SPIDER) {
            return std::string("Giant Spider");
        if (monster.type == MonsterType::OGRE) {
            return std::string("Ogre");
        if (monster.type == MonsterType::ORC) {
            return std::string("Orc");
        if (monster.type == MonsterType::SLIME) {
            return std::string("Slime");

        // In case we entered something else
        return std::string("???");

    void printMonster(Monster monster_real) {
        std::cout << "This " << getMonsterTypestring(monster_real) << " is named " << << " and has " << << "health\n";

    int main() {

        Monster ogre = { MonsterType::OGRE, "Torg", 145 };
        Monster slime = { MonsterType::SLIME,"Blurp", 23 };


        return 0;

  • Jonathan

    The longest code I"ve ever wrote! Please give me some comment!

    • Jonathan

      I've updated a bit.

      • * Initialize your variables with brace initializers. If you add a member to @monsterData and forget to assign to it in @getMonsterInfo, this member will have an undefined value. Either initialize @monster, or all members in the struct definition.
        * You're using the same name style for variable, functions, and types. This will lead to confusion.
        * Avoid abbreviations. The time you save writing them is time wasted reading them. Code is more often read than written, you're wasting time.
        * Don't pass 32767 to @std::cin.ignore. Pass @std::numeric_limits<std::streamsize>::max().
        * @getTBDA: You don't need temporaries, you can return directly

        * @traitString can always be determined by @trait. Remove the member and add a conversion function, just like you did with @getTypeString.
        * Inconsistent formatting. Use your editors auto-format feature.
        * @getTypeString::num should be an @monsterType.
        * Line 116, 123: Don't use string concatenation to print, use the stream's @operator<<.

        • Jonathan

          thanks for the detailed suggestions! For the function of getting string, is it better to use switch() instead of using if/else statement? I just go through the control flow!

          And for the abbreviation, I feel like "TBDA" seems to be more readable than "TraitBloodDefenceAttack".

          • > is it better to use switch() instead of using if/else statement?
            Whenever you have a limited set of values (eg. char, enum), use a switch. The compiler can optimize switch-statements better than if-statements.

            > I feel like "TBDA" seems to be more readable than "TraitBloodDefenceAttack"
            You might understand it, but everyone else who reads your code has no idea what TBDA is supposed to mean. And you won't either, if you look back at your code in a couple of months or years (You might not look back at this code, but some projects will require maintenance after a long time).

  • Merlin

    Is this a problem if I don't define an enum class? There is a shorter way and it works fine!
    (like the solution)

    I would really like to hear your thoughts about it, thanks! :)

  • Dimbo1911

    Any advices or suggestions on the following?

    • Hi!

      * Line 14, 15, 16: Initialize your variables with brace initializers.
      * @main: Missing return-statement.
      * Line 23-29 should use "else if". (Covered next chapter)
      * Line 39: Unnecessary space before line break.

      What's up with the Xs in front of every comment? It makes them harder to read.

      • Dimbo1911

        Thank you for your input, is there any difference in "if" and "else if", if every of the cases will result in return statements?
        Since they are not real comments but more of a to do list (I usually do not keep them in code, or move them to a different .txt file), I keep track of stuff I have doen with putting X in front of it haha

        • > is there any difference in "if" and "else if", if every of the cases will result in return statements?
          No. If conditions exclude each other, they should be in else-ifs. That way, if you decide to remove the return or replace it with something else, your code will still work as expected. It also allows a reader to understand your code without having to look at the if's body.

  • Mitchell Zakocs

    Just finished the quiz question, would love any criticism you can provide.

    • Hi Mitchell!

      * Line 12, 13, 14: Initialize your variables with brace initializers.
      * Line 32: Limit your lines to 80 characters in length for better readability on small displays.
      * Line 20ff: Should be else-if.

  • Alireza

    Hi there,

    I've done that quiz. I think I've just used another way to do that, however.

    Is this code good to use the same ?

    • * Line 15, 16, 65: Initialize your variables with brace initializers. You used copy initialization.
      * Line 18, 21: Initialize your variables with brace initializers. You used direct initialization.
      * Line 15: Use @std::string's default constructor (ie. don't pass arguments).
      * Line 30-50: Should be else if.
      * @printMonsterStat doesn't need a forward declaration if it's declared above @setMonsterStat.

      They're called ogre.

  • Brian Gaucher

    I completed it solving all my issues alone, without peeking.
    But could I improve anything. (Looking for feedback)

    I also typed it all in Dvorak Programmer layout.

    • Hi Brian!

      * Line 13, 14, 15: Initialize your variables with uniform initialization.
      * @printType, @printMonster: Bad name
      * @printType: If you have a limited set of values, use a switch. It allows for better compile-time optimization.
      * @printType: Return a const char *. Constructing an @std::string every time @printType is called is slow.
      * @main: Missing return value

      > I also typed it all in Dvorak Programmer layout
      Let me know how it went once you got used to it. I've never learned it, because I'm afraid I'll forget qwerty and be lost when I have to use a regular layout. Switching from qwertz (ger) to qwerty (us) was a good step for me.

  • Rai

    I decided to make a small RPG. I'm having some problems so if anyone could help me out here.




    I was testing some stuff like auto and typedef.



    2. This works but I believe it causes a segementation fault?! The console just goes blank after you put a number. I tried with an online copiler instead and it showed an segementation error after std::cin >> number
    It seems to be std::string userFavColour causing the problem. (this happens when I type in the std::cin.ignore command to fix the first problem)

    3.Also I was wondering how to forward declare a enum statement, because all my code had to be squished into main.cpp

    • * Initialize your variables with uniform initialization
      * Use your editors auto-formatting feature and use curly brackets
      * Read compiler warnings and fix them
      * Use enum class instead of enum
      * Don't call @std::string::string manually
      * Inconsistent use of 'or' and '||'
      * Don't use @int16_t. Use @std::int_fast16_t or @std::int_least16_t
      * Line 151, 155: @printColour is called twice without the argument changing inbetween
      * Line 154, 155: Should be guarded by the if-else-statement below
      * Magic numbers

      @std::cin::operator>> extracts until '\n' and leaves '\n' in the input stream.
      @std::getline extracts everything and removes the '\n'. If '\n' is left in the input stream after an @std::cin.operator>> operation, @std::getline will extract the trailing '\n' and stop extraction. You need @std::cin.ignore

      You wrote 'n', not '\n'. @std::cin.ignore runs until it finds a 'n'. There is no 'n'. So it runs indefinitely.

      Use enum class. Enum class can be forward declared like everything else.
      If you want to forward declare an enum, you have to specify its size

      • Rai

        Thank you. The main problem was that I used 'n' instead of '\n' for std::cin.ignore. Silly me.

        why use int_fast16_t or int_least16_t ? whats the difference?

        where did I call std::string::string manually?

        Can you not forward declare enum class? I tried this but wasn't working.

        • > why use int_fast16_t or int_least16_t ? whats the difference?
          @std::int16_t is implementation defined, ie. not all compilers support it.
          @std::int_least16_t is the smallest integer type with at least 16 bits.
          @std::int_fast16_t is the fastest integer type with at least 16 bits

          > where did I call std::string::string manually?
          Line 96, 98, 100, 101, 108, 110, 112, 114, 115, 125. You didn't in @getMonsterIDString

          > Can you not forward declare enum class? I tried this but wasn't working.

  • Boteomap2

    Hi... let give me some advice for code better....



  • Dean Cutillar

    I wrote a program to solve this assignment but I used a enum class called "monsterType", which held the type of monster, and a class called "individualMonster", which held the type, name, and health points as members.

    I got it working with an array of type "individualMonster", and wanted to have it work with a vector of "individualMonster".  

    My program has the user input all the monster info, from the keyboard.

    I was able to get it to work using regular for loops, but was not able to print out the vector using a "for each" loop.  Below is the code for the program.  Please let me know how to code it using a for each loop.  Thanks.


    #define MAX_MONSTERS 5

    enum class monsterType {
        OGRE = 1,

    class individualMonster {
        monsterType m_type;
        std::string m_name;
        int m_health;
        monsterType setMonsterType();
        void setMonster();
        void printMonster();

    monsterType individualMonster::setMonsterType() {
        bool validInput = false;
        int userInput;
        while (!validInput) {
            std::cout << "Please enter monster type: \n";
            std::cout << "Enter numbers\n1) Ogre\n" << "2) Dragon\n" << "3) Orc\n" <<
                "4) Giant Spider\n" << "5) Slime\n";

            std::cin >> userInput;
            std::cin.ignore(1000, '\n');
            if ((userInput > 0) && (userInput < 6))
                validInput = true;
                std::cout << "Please enter number between 1 and 5\n";
        return static_cast<monsterType>(userInput);

    void individualMonster::setMonster() {
        m_type = individualMonster::setMonsterType();
        std::cout << "Please enter monster name: ";
        std::cin >> m_name;

        bool validInput = false;
        while (!validInput) {
            std::cout << "Please enter monster health with a number greater than zero, less than 100:\n ";
            int userInput;
            std::cin >> userInput;
            std::cin.ignore(50, '\n');
            if ( // has a previous extraction failed?
                // yep, so let's handle the failure
                std::cin.clear(); // put us back in 'normal' operation mode
                std::cin.ignore(32767, '\n'); // and remove the bad input
            else {// else our extraction succeeded
                m_health = userInput;
                validInput = true;

    void individualMonster::printMonster() {
        std::cout << "This";
        switch (m_type) {
        case monsterType::OGRE:
            std::cout << " Ogre ";
        case monsterType::DRAGON:
            std::cout << " Dragon ";
        case monsterType::ORC:
            std::cout << " Orc ";
        case monsterType::GIANT_SPIDER:
            std::cout << " Giant Spider ";
        case monsterType::SLIME:
            std::cout << " Slime ";
            std::cout << " Unknown";
        std::cout << "is named " << m_name << " and has " << m_health << " health.\n";

    int main() {
        std::vector<individualMonster> monsterArray[MAX_MONSTERS];

        bool userDone = false;
        int counter = 0;
        while (!userDone) {
            individualMonster temp;
            std::cout << "Enter details for Monster number: " << counter + 1 << std::endl;
            std::cout << "Done entering Monsters? \n";

            std::string userResponse;

            std::cin >> userResponse;
            if (userResponse == "y") {
                userDone = true;

        std::cout << "Here are your Monsters: \n";
        for (int index = 0; index <= counter; index++) {
        /* int ind = 0;
        for (individualMonster &index : monsterArray) {
            std::cout << "index number " << ind << std::endl;
            std::cout << "index number " << ind << std::endl;
        }  */

        //pause code
        int pause;
        std::cin >> pause;
        std::cin.ignore(1000, '\n');

        return 0;

    • @monsterArray is an array of vectors. It should be

      Once you've done that, the loop you commented out will work. It will break other parts of your code, which you have to fix.

      * Initialize your variables with uniform initialization
      * Read the documentation of @std::cin.ignore
      * Don't use preprocessor macros for constants
      * You're using the same name style for functions, variables and types. This will lead to confusion
      * @monsterType::OGRE doesn't need to be set to 1, because 1 is the default value
      * You don't need to return from a void
      * Inconsistent use of curly brackets. Always use curly brackets

  • Ajalle Perfej

    The solution just returns a string constant and then prints what is returned to the console. Is there a way to have the monster names and health assigned to variables connected to the relevant struct enums?

  • mjr

    I've been looking over this and I don't know why it isn't working.

  • Outrageous Gem

    How would I sort this programm if I wanted to separate it into multiple files?

    "enum class MonsterType" and "struct Monster" could probably just be defined inside a header "monster.h" but where would I put "getMonsterTypeString(Monster monster)" ? Put it into a monster.cpp and forward declare it in monster.h?

  • emanon

    I have 2 questions.

    why did we have to use "monster.type" here? I dont really understand the use of the "."
    and the next question is,

    why did we use the "::" here?

    I probably should revisit where that was explained but I coudnt find it, it would be very kind if you can tell me which lessen to reread, thank you very much!

  • kaden

    my program is not working
    i can not find the reason for 2days.
    is there any problem in my code?

  • DAT


    enum class Monster

    struct MonsterDescript
        Monster type;
        int health;
        std::string name;

    std::string monsterType(Monster x)
        if (x == Monster::ORC)
            return "Orc";
        else if (x == Monster::ORGE)
            return "Orge";
        else if (x == Monster::SLIME)
            return "Slime";
        else if (x == Monster::DRAGON)
            return "Dragon";
            return "Unknown";

    void printInformation(MonsterDescript x)
        std::cout << "this " << monsterType(x.type) << " is named " << << " and has " << << " health.";
        std::cout << "\n";

    int main()
        MonsterDescript adam{ Monster::ORC,145,"Stupid" };
        MonsterDescript eva{ Monster::DRAGON,235,"Adam" };
        return 0;

Leave a Comment

Put all code inside code tags: [code]your code here[/code]