Six222

.

I think it depends what your working on.. You'll probably want to imagine a world and a basic story line and design out some specific mechanics. For a good game you'll need to have a mind of how your mechanics would interact/work with/in your world and heavily prototype.

Maybe because this is a simple asteroids game? Does he need to bother with new fancy C++11 features at this time?

Well it's well worth the read even if he is making a simple game. C++ 11 offers better ways of doing things such as the new random which can create a better distributed random number...

A class hierarchy is what i dont want to do, i want to stay away from inheritance because it will create spaghetti code when creating more and more code. I just wish there was an example of a basic Entity system

And how do you know this, have you tried writing an application in this way? Yeah it CAN lead to spaghetti code only if you design it poorly. You should never just take advice from the internet and say that it's bad beacause somebody said so..

Isn't the issue that OP needs to use a custom deleter to dispose of the allegro created pointer with the appropriate allegro function?

i.e.

BitmapList[filePath] = std::shared_ptr<ALLEGRO_BITMAP>(al_load_bitmap(fullPath.c_str()), al_destroy_bitmap);

or whatever

Yeah that was the answer, but as everyone seems to be saying I'm curious as to why std::make_shared should be used?