Re: Garbage Collection - The Trash Begins To Pile Up
In article <Z76dnR73I66gygTYnZ2dnUVZ_oipnZ2d@comcast.com>,
Walter Bright <firstname.lastname@example.org> wrote:
For the potential problem with the free store, just throw an exception:
Object *o = new Object();
foo(); // foo() throws an exception, o is now leaked
And how does does GC magically fix this code?
There are two bugs here: the memory leak, and that Object may never be
destroyed. GC can only address the first one.
Unless the caller knows that Object only manages memory, the code is
still just as buggy. And I really don't want a tight coupling between
Object and everyone that uses it. The users of Object should not have
to know about its internals; otherwise, we have effectively eliminated
encapsulation and data hiding.
If I write the code as:
std::auto_ptr<Object> o(new Object());
foo(); // foo() throws an exception, o is NOT leaked
I don't have the leak, the non-destruction bug, nor the tight coupling.
You've got such potential every time you use free store. And every time
you use RAII, you have the potential for a dangling pointer.
And every time you use GC you have the potential of a non-destruction
Don't get me wrong; I want GC. But this is a real issue with it.
Nevin ":-)" Liber <mailto:email@example.com> 773 961-1620
[ See http://www.gotw.ca/resources/clcm.htm for info about ]
[ comp.lang.c++.moderated. First time posters: Do this! ]