On Thu, Mar 25, 2010 at 10:30:42AM -0400, Greg A. Woods wrote: > indeed, and memory "frees" itself at exit time too, and calling free() a > whole lot of times on a sure path to exit() is a pedantic waste of time > and code (and thus maintenance). OTOH properly releasing memory on exit paths makes hunting for memory leaks _much_ easier. Gabor