>>2
Why would the fact that all heap blocks were freed this time imply that they will all be freed every time?
Through thorough testing, dickbag. Consistently, every time, I get this, every argument and every combination of bytecodes in the file it reads. God damn, why are you so skeptical? I was relishing my success at automating an efficient and effective cleamup routine and you assume it took the only branch where there are free()s.
Did you consider all the mallocs happen with resources that are managed carefully in a self contained unit of memory resources so as for easy access and easy cleanup? Some people on
/prog/ can program, you know.
Go play with your REPL.