Aktuelle Änderungen Printable View Änderungen Bearbeiten
ConcurrentProgramming > StaticVsDynamicTyping > InteractiveProgramming > IncrementalCompilation > ModelDrivenProgramming > ModelDrivenArchitecture > ArtificialIntelligence > VeryHighLevelLanguages > DocumentationIndex > ThePragmaticProgrammer > PragmaticProgrammers > DenkzeitWikiCommentSpam > DomainSpecificLanguages > HackingClojureWithEmacs > PythonObjectPersistence > DynamicMemoryAllocation > HeapClear Trail
(weitergeleitet von Main.DynamicMemoryAllocation)
GarbageCollection
CSharp
HeapAndStack
Variables on the Stack can be accessed faster. The Stack is not managed, overhead is not neaded. Variables on the Stack are removed when they run out of scope.
CSharp
HeapAndStack
In theory, I suppose, the programmer shouldn't be forced to consider mundane details of hardware such as heap and stack storage. And yet, what I think I've concluded from my experience with C# is that the difference between the heap and stack is so fundamental that the programmer really must consider the differences to write efficient code.[1]
The Stack is a Hardware Supported Feature in terms of Microprocessor Registers and Segments.
The Heap is actually a Software Abstraction.[2]
- http://www.codeguru.com/forum/showthread.php?t=350945 --Stack vs Heap ??
- http://www.codeguru.com/forum/showthread.php?p=1164413#post1164413 --The Stack & Compiler Relationship
- http://www.codeguru.com/forum/showthread.php?p=1164413#post1164413 --The Stack & Compiler Relationship
- http://www.albahari.com/value%20vs%20reference%20types.html --C# Concepts: Value vs Reference Types
Variables on the Stack can be accessed faster. The Stack is not managed, overhead is not neaded. Variables on the Stack are removed when they run out of scope.