Let’s look at these independently: This loop, intuitively, means “keep reading values from cin into x, and as long as a value can be read, continue looping.” As soon as a value is read that isn’t an int, or as soon as cin is closed, the loop terminates. This means the loop will only execute … Read more
-Wall doesn’t include many options. -Wconversion is one of them and warns about the behavior you’re interested in. See http://gcc.gnu.org/onlinedocs/gcc/Warning-Options.html
You’re trying to pass a char to LoadFileToString which takes in a char*. I think what you intend to do is this Notice that I’m reading the input into a string instead of a char since the LoadFileToString expects a (C-style) string to be passed in; instead you’re reading and trying to pass a character … Read more
std::stoi was introduced in C++11. Make sure your compiler settings are correct and/or your compiler supports C++11.
The literal 0 has two meanings in C++.On the one hand, it is an integer with the value 0.On the other hand, it is a null-pointer constant. As your setval function can accept either an int or a char*, the compiler can not decide which overload you meant. The easiest solution is to just cast … Read more
If you call the function with a first argument of 0 the loop is never executed and the return statement is, thus, never reached. Falling of the end of a non-void function is undefined behavior. My personal guess is that the return statement was meant to one level up, i.e., in the out block: this would guarantee that the function always returns … Read more
It for example happens in this case here: Try using std::string instead of just string (and include the <string> header). C++ Standard library classes are within the namespace std::.
In State::State, you are using Core before it is actually defined. You can fix this easily in your example by moving the constructor implementation out of the class definition: It’s much more common in practice to have the implementation of these functions in a separate implementation (.cpp) files, in which case the forward declarations would … Read more
In C++11, in-class member initializers are allowed, but basically act the same as initializing in a member initialization list. Therefore, the size of the array must be explicitly stated. Stroustrup has a short explanation on his website here. The error message means that you are providing too many items for an array of length 0, … Read more
It’s very unfortunate that you see dynamic allocation so often. That just shows how many bad C++ programmers there are. In a sense, you have two questions bundled up into one. The first is when should we use dynamic allocation (using new)? The second is when should we use pointers? The important take-home message is … Read more