C
Chris Dunaway
I have seen on these newsgroups many posts about value types and
reference types. And, generally speaking, value types are allocated on
the stack, and reference types on the heap.
My question is about the stack and heap itself. Is the stack really a
stack? is ia LIFO data structure? Does each program have its own
stack?
What happens when a value type is dim'ed? What is actually stored on
the stack and how is it organized? When a reference type is dim'd what
happens? Is the reference itself stored in the stack at compile time
and then the object created at runtime?
Can you point to any articles that explain the theory of how types are
allocated on the stack and heap as well as some details about how the
stack and heap works? I am just trying to find an article that
explains it. Not necessarily how it works in .Net, but in general,
although a .Net explanation would be helpful.
Thanks,
Chris
reference types. And, generally speaking, value types are allocated on
the stack, and reference types on the heap.
My question is about the stack and heap itself. Is the stack really a
stack? is ia LIFO data structure? Does each program have its own
stack?
What happens when a value type is dim'ed? What is actually stored on
the stack and how is it organized? When a reference type is dim'd what
happens? Is the reference itself stored in the stack at compile time
and then the object created at runtime?
Can you point to any articles that explain the theory of how types are
allocated on the stack and heap as well as some details about how the
stack and heap works? I am just trying to find an article that
explains it. Not necessarily how it works in .Net, but in general,
although a .Net explanation would be helpful.
Thanks,
Chris