A garbage collector should be added into VaVoom to ensure that no memory leaks or segmentation errors occure. A generational GC is simular to the GC Java uses but it keeps track of how old an object is in the theroy that once an object has been around for a long time it is less likely to become garbage--it also treats as garbage any pointer-strucure that can no longer be referenced by other parts of the program--in case a pointer is discarded without bothing to delete the rest of the objects it was pointing to. It is more effecient for a RT (real time) system such as VaVoom to do GC operations incrementally rather than stoping gameplay for a batch GC. Most OO languages and IDEs use GCs to free a programmers/level designers time and allow them to focus on the issues thay want without worrying about memory costs.

Yes, a garbage collection is a planed feature. And I'm planing to do this really soon.

[shadow=blue,left,300]<br>The type of GC is an important choice--it should be<br>built in like the one in Java, and prevent memory leaks.<br>[/shadow]<br><br>[tt]<br>The GC must work in RT so that game play is not<br>adversely affected when the garbage must be collected.<br>[/tt]<br><br>Types of GCs (+ benefits):<br>[list:gq9op591]<br>[*:gq9op591] Empherial -- Makes sure only true garbage is discarded.<br>[/*:m:gq9op591][*:gq9op591] Generational -- keeps older stuff that has lasted.<br>[/*:m:gq9op591][*:gq9op591] RT -- does collection while program is running rather that pause program.<br>[/*:m:gq9op591][/list:u:gq9op591]