Starting a new game does not reuse objects.

[Daniel Bell]

After loosing all life and the game over screen is presented to the user there is an option to: "Start a new game". When you start a new game it creates a whole new set of objects into memory instead of reusing the ones that were created in the previous game.

This in itself is not a huge issue when you are only playing 1-2 games (yet its unnecessary), but when you get into larger series of games (20-30 "new games") then there are serious issues with memory being used up.

[Daniel Bell (danielbell)]

Hopper as of r51 should now properly re-use objects when possible.
Game now should have less loose references and less cycles where references could be tied up, thus making the collecter able to dump objects properly that are no longer used. This should hopefully fix the issues within the game, memory wise.

[Daniel Bell (danielbell)]

r55 introduced a regression where the game no longer reuses objects, inorder to fix the issue where difficulty was not being updated.

[Daniel Bell (danielbell)]

r56 fixes this, it uses a dirty hack to bypass the problem where difficulty was not updated since the class was already instantiated and with difficulty being set in the constructor meant that the difficulty changes were not reflected in the class.

This now allows you to change difficulty within the play_levels() function, via an optional paramater. This paramater when not Nothing will change difficulty within the instantiated class, removing need to recreate it. Only problem here is that its an ugly hack, where since difficulty is only speed we can get away with.