Variable Scope & Memory Visualizer | 變數範圍與記憶體視覺化工具

Learning Objective

Understand how computer memory manages variables. Learn the lifecycle, accessibility, and boundaries of variables defined in different scopes.

Concept Explanation

Variables exist in different memory segments based on where they are declared. Understanding these boundaries is critical for writing bug-free algorithms and optimizing system resources.

Common Misconception

"Local variables can be accessed anywhere after the function is executed."

Reality: False. When a function finishes execution, its Execution Context is popped off the Call Stack. All local variables declared inside are immediately destroyed.

Key Takeaways

Global Variables live until the program terminates. They use persistent memory.
Local Variables only exist within the specific function or block they are defined in.
Attempting to access a local variable outside its block results in a Scope/Compilation Error.

Think & Link

What happens if a local variable has the exact same name as a global variable?

Fun Fact

Every function call consumes a small amount of stack memory \( O(1) \). A recursive function without a base case will exhaust all memory, causing a fatal crash known as a Stack Overflow.

Code Execution

global_var = "Earth"

def explore():
    local_var = "Mars"
    print(global_var)
    print(local_var)

explore()
print(global_var)
print(local_var) # ERROR!

Click 'Next' to start execution.

Terminal Output

> System Ready...

Memory Visualizer

Global Scope (Heap / Data)

Self-Assessment

1. Where are local variables typically stored during execution?

2. Will the program crash if you print a global variable inside a function?

Score: 0/2

Code Execution

Terminal Output

Memory Visualizer

Scope Error

Self-Assessment