Commonly Confused Tidbits re .NET Garbage Collector

votes

Commonly Confused Tidbits re .NET Garbage Collector

Entropy Overload – I recently read a less than informed blog post purporting to describe the .NET garbage collector, but when pressed to point to a better one, I couldn't find a single concise article that covered everything I thought should have been covered. Type and Memory Safety We all know what the gist of GC is about: you allocate new objects, but don't have to worry about freeing them. Combined with type safety in the language, this can give you another kind of guarantee, memory safety: that it's impossible to create a dangling pointer (a pointer to freed memory). Type safety's "safety" is compromised ...

Favorite? Off-Topic? Barry Kelly @ 2009-12-14 17:16