To answer the first part of your question, you must create an object of type Player before you can use it. When you say push_back(Player), it means “add the Player class to the vector”, not “add an object of type Player to the vector” (which is what you meant). You can create the object on the stack like … Read more
The class declaration goes into the header file. It is important that you add the #ifndef include guards. Most compilers now also support #pragma once. Also I have omitted the private, by default C++ class members are private. and the implementation goes in the CPP file:
I think there is no shortcut key for this purpose in Visual Studio but If you use ReSharper you can use Ctrl + Shift + /. Have a look at this may be useful as well.
The difference is more prominent when you are passing a big struct/class. when you use use ‘normal’ parameter, you pass the parameter by value and hence creating a copy of the parameter you pass. if you are using const reference, you pass it by reference and the original data is not copied. in both cases, … Read more
It allows the differentiation of bitwise const and logical const. Logical const is when an object doesn’t change in a way that is visible through the public interface, like your locking example. Another example would be a class that computes a value the first time it is requested, and caches the result. Since c++11 mutable can be … Read more
You’re close. Note that you can define it inside the for loop: And if you are using C++11 then you can use a range-based for loop instead: Here auto automatically deduces the correct type. You could have written Student const& i instead.
Each instantiation and full specialization of std::atomic<> represents a type that different threads can simultaneously operate on (their instances), without raising undefined behavior: Objects of atomic types are the only C++ objects that are free from data races; that is, if one thread writes to an atomic object while another thread reads from it, the behavior is … Read more
You aren’t actually overriding the sort function, so MergeSort is still an abstract class: These sorts have different signatures, so they are different functions. To solve this, you either need to change your MergeSort::sort method to not take in a low and high argument, or to add a low and high argument to your other sort methods.
If you always want the loop to execute at least once. It’s not common, but I do use it from time to time. One case where you might want to use it is trying to access a resource that could require a retry, e.g.
You are declaring the function bodies inside the main function, which is not valid. Also you’ve been using too many ‘}’-s. Your code should look more like this: