There was a post about garbage collection today, which is a topic I haven''t actually heard of until now. From what I hear, the idea is that it looks through your program''s memory all the time, and deletes any variables you haven''t deleted that you should? Or, it deletes it at the end? It sounds like it could make for some pretty lazy programming... But, it does sound like it could be cool for debug. Are there any free (possibly opensource) garbage collection libraries out there? ------------------------------ Jonathan Little invader@hushmail.com http://www.crosswinds.net/~uselessknowledge

Depends on the garbage collection algorithm. Some algorithms work in a separate thread, doing periodic scans of memory checking for orphans. When an orphan is found it''s deleted and/or logged. Others are more agressive and track almost every memory access trying to determine if memory is orphaned. These are IMO more useful in debugging. They also cripple your performance while running, so you almost have to have a two separate debug builds.

Some people for debug like to use basic leak detectors. They just log every memory allocation and deallocation and deallocate ophaned memory upon program termination.