yeah it works alright now
yeah it works alright now
I have a bunch of classes now, should I worry about writing destructors for them or memory will be freed autimatically when app terminates?
when it comes to classes whatever you create you must destroy. you should get heap trace up and running if you don't already. check the output file often to check mem leaks as you go along. also make sure to free up any opengl stuff in your destructors.
ok, thanks. list of leaks is so long that it doesn't fit on the screen
I built my frame work using a custom linked list design. all things are connected so I worry little about mem leaks. I worked on it for over a year before I started checking for leaks and I wasn't really surprised that I had none. so much more is possible with such a design.
this will probable explain it much better then I could
mine is a single linked looped list and I am using an array of children which makes it possible for each and every class to maintain any number of lists without a container class to manage them. I will try to extract it from my code if you really want it. I plan to release my framework when it is finished but I can't really say how long that will be.
http://en.wikipedia.org/wiki/Linked_list
Bookmarks