This is because you have not allocate your objects prior to using them: It’s worth adding that using pointers in this situation is, well, pointless: string objects in the standard C++ library allocate the data for the string from the heap; strings are usually not much more than a pair of pointers anyway.
This is a simple problem. You just forgot the semi colon at the end of your header file. The compiler errors you get for missing the semi colon at the end of a class definition are very hard to relate to the actual problem – just get in the habit of checking that when you … Read more
It looks good. You only need to add a ./ before your executable. Without it, valgrind fails to find it and reports ‘command not found’.
Does something along these lines exist? No. With the stl map class, you use ::find() to search the map, and compare the returned iterator to std::map::end() so Obviously you can write your own getValue() routine if you want (also in C++, there is no reason to use out), but I would suspect that once you get the hang of using std::map::find() you won’t … Read more
You haven’t posted the findvertex method, but Access Reading Violation with an offset like 0x00000048 means that the Vertex* f; in your getCost function is receiving null, and when trying to access the member adj in the null Vertex pointer (that is, in f), it is offsetting to adj (in this case, 72 bytes ( 0x48 bytes in decimal )), it’s reading near the 0 or null memory address. Doing a read … Read more
Those error messages or just mean that CMake was unable to find your C/CXX compiler to compile a simple test program (one of the first things CMake tries while detecting your build environment). The steps to find your problem are dependent on the build environment you want to generate. The following tutorials are a collection … Read more
You should be using single quotes for characters. Double quotes means you’re using a (potentially single-character) string literal, which is represented as a const char * (pointer to constant character). Correct syntax: circle1.symbol = ‘*’;
it should be next = newNext; instead of next = newNext->next;
C++11 rules for automatic generation of special members aren’t as simple as you posted them. The most important distinction is that in some cases, the member is implicitly declared, but defined as deleted. That’s what happens in your case. C++11, [class.copy]§11: A defaulted copy/move constructor for a class X is defined as deleted (8.4.3) if … Read more
This is not a compiler error: the error is coming from the linker. After compilation, the linker will merge the object files resulting from the compilation of each of your translation units (.cpp files). The linker finds out that you have the same symbol defined multiple times in different translation units, and complains about it … Read more