> As for the "memory leaks" --- I haven't looked at the source, but something whose runtime is very short-lived, like pkg-config... To be fair in the other dir

> As for the "memory leaks" --- I haven't looked at the source, but something whose runtime is very short-lived, like pkg-config... To be fair in the other direction, it's a minority of interesting software projects that don't care about memory leaks. Also, there are ways to "skip" freeing memory in C++ safely using appropriate allocators. In actuality, you'd have your allocator, in its destructor, clean up itself and all its objects at the same time. It's nearly the same performance without sacrificing correctness or lowering standards with respect to leaking memory.