> > > 
> > > The problem with GC is that it has a tendency to make programmers
> > > forget that memory management is important.  Even with GC, you still
> > > have to worry about memory leaks and memory usage.  With languages
> > > such as C and C++, you *must* pay attention to these things, while GC
> > > often allows programmers to forget about these things because GC
> > > handles a lot of this stuff behind the scenes.
> > No you don't.  You're thinking about GC in languages that weren't designed
> > for it.
> 
> No, this animal really does exist in Java.  Actually, it is a major
> issue in Java.  If it wasn't a major issue in Java, then at least one
> major article in an issue of Doctor Dobb's Journal was a complete
> lie.  A prominent example of this is you pass an object to another
> object as a listener.  If you forget to remove the former object from
> the latter object, the former object will never be GCed as long as the
> latter object exists.
I think you misread the article.  No such bug/issue exists in Java.  The
listener example holds, but has nothing to do with private/protected.
That is an example of giving a reference to a datastructure and forgetting
you've done so.  Its not a memory leak.  A memory leak is when all
references to an allocated block of memory are lost and no mechanism
exists to reclaim it.

        Scott


_______________________________________________
Freenet-dev mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/mailman/listinfo/freenet-dev

Reply via email to