From the course: CLR Memory Management for Developers

Unlock the full course today

Join today to access over 22,400 courses taught by industry experts or purchase this course individually.

Static stack heap

Static stack heap

From the course: CLR Memory Management for Developers

Start my 1-month free trial

Static stack heap

- [Instructor] So once we've got that big empty space to work with, how exactly do we partition that up? Well fundamentally, there's three different kinds of storage, much of which you've probably already worked with to some degree but never really thought about formally. The first is what we call Static Storage, that is to say, any name in your program is bound to memory at compile time. Usually this goes by the more technical term global, which is generally considered a bad thing in most modern languages. There's a lot of places where in fact, we use globals as a part of our programs where they're not considered bad. A, we call them singletons, or B, in some cases, when we refer to costs or when we actually have static members, that is to say static fields, inside of an object, that's basically Static Storage. We bind a particular address to that name, and typically that won't change throughout the lifetime of the program, particularly in native managed languages. The problem with…

Contents