activation record造句

Each call gets its own activation record, so each time it is called the variables get their own storage space within that activation record.

This makes it easy for functions to know where their activation record is — they are simply defined in terms of the stack pointer.

Because activation records are implemented on a stack, they are often referred to as stack frames, but both terms are equivalent.

As you can see, the suspended function activation records "stack up", and then, when each function returns, it gets taken off of the stack.