Elysian Shadows

You have to think about how you will use the stack and then choose the implementation to squeeze out the last bit of performance if you really need that, in terms of asymptotic complexity a vector and a doubly-linked list are equal. However, a list will only hold the objects that are actually on the...

Pretty much the same as you would normally do except for that one include and leaving out the cpp file in the compilation process. Array.h includes Array.cpp at the end of the file, just before the #endif of the guards. You can leave the #include "Array.h" in the Array.cpp file, if your ID...

The problem is that the compiler needs to see the actual code of your functions when it instantiates a template, since it has to produce code for that concrete type and can no longer stay on a generic/templated level. Instantiation happens when the compiler sees that you wrote saArray<unsigned short...

generic insertion sort I used in a situation where I knew an array was partly sorted already, cmpFnc has to be a class/struct with an operator() that realizes a "strictly less than" comparison template <class T, class ComparisonFunctor> void insertion_sort(std::vector<T>& arr, Comparis...

Uhm, looks pretty complicated. First thing I noticed in your initial post is that "\\content\\images\\background.bmp" is not a relative path, at least it wouldn't be in linux and I'm pretty sure it neither is in windows. If you want a relative path leave out the leading backslashes or writ...

The player drawing is fine. The tile drawing is probably not doing what you want it to, I think. You are doing rect.x =c - myCam.getX() but c is just the number of the tile (0, 1, 2, etc) but it should be scaled by the tile width: rect.x = c * tW - myCam.getX(). The same goes for rect.y. Right now t...

You should have "world" coordinates and "view" coordinates. All the game objects positions are in world coordinates and only those are used in the game logic including collision detection. Drawing is seperate and you just translate world coordinates to view coordinates (using the...

Are you sure that function is even invertible? If the output of 2 different (or more) inputs it the same, how can you know which one was the correct one after decrypting? That's the point of most cryptographic hash functions anyway.

Back to vtables, does the vtable lookup involve iterating through the table? If so then it's O(n). The wikipedia article says no. Since the compiler knows about all virtual functions at compile time it can also come up with a static "name to table-index" mapping that won't change at runti...

It's just some notation to describe (algorithmic) complexity. O(n) means an algorithm that has some sort of input of size n runs in linear time (e.g. finding the maximum in an array of n ints). O(1) means constant time, so regardless the input size it takes a constant amount of time/steps to run. wi...

Arce wrote:Though not by much? Probably O(1), O(n) if it's really gay. If anybody has time to google it lemme know. ;p

I'm pretty sure it's O(1) in the sense that for any class hierarchy it takes only 1 table lookup at runtime to find the function to be executed.

Yea it should work like this: ifstream is; is.open("filename", ios::binary); is.seekg(0, ios::end); unsigned int length = is.tellg(); is.seekg(0, ios::beg); char* buffer = new char[length]; is.read(buffer, length); It should load the whole file into that byte array buffer and I guess it wi...

thank you for all of your help! everybody!! now, fantastico, about the filen.size() is there a way to do that so that i actually get the stream size instead of name of file? Taken from http://www.cplusplus.com/reference/iostream/istream/tellg.html : is.seekg (0, ios::end); int length = is.tellg(); ...

Ginto8 wrote:or you could do filei.read((char*)&loader, ... )

The compiler would accept it, the OS and the programmer wouldn't like the result though

well i put the '&' before "loader" now and i get this (line 18) error: no matching function for call to `std::basic_ifstream<char, std::char_traits<char> >::read(std::string*, size_t)'| That's because you are passing the function a pointer to a std::string while it's expecting a point...