Was this helpful?
Call Stack: Administering function calls
A call stack is composed of one or many several stack frames. When a function is called, a new stack frame is created corresponding to the function invoked. This stack frame holds the pointer to the function that itself is stored in the heap memory. In addition, the arguments to the function, its local variables, and the return value are also stored in the frame. In other words, each stack frame represents a call to a function which has not yet terminated with a return including the frame of data that gets pushed onto the stack. At function return, its frame is popped off from the stack. Since the call stack is organized as a stack data structure, a function invoking another function will result in pushing another frame on the top of the call stack, and so on, with the information stacking up and unstacking as the program dictates.
Note that for the sake of simplicity, the fact that the console.log calls are also pushed onto the call stack has been deliberately omitted.
|posted||Sep 12, 2016|
|active||Sep 12, 2016|
|•||Reflection in .NET - Part 1|
|•||Updating a CSS class property in real-time|
|•||Client-side MVC pattern|
|•||Serialization in .NET - Part 4|
|•||Serialization in .NET - Part 3|
|•||Serialization in .NET - Part 2|
|•||Serialization in .NET - Part 1|
|•||How to create pretty URLs in Angular|
|•||In Angular what is the difference between ngRoute and ui-router|