# Let's Build A Simple Interpreter. Part 17: Call Stack and Activation Records

DevFeed: [Let's Build A Simple Interpreter. Part 17: Call Stack and Activation Records](<https://devfeed.tech/articles/let-s-build-a-simple-interpreter-part-17-call-stack-and-activation-records-33320.md>)

Original publisher: [Read original article](<https://ruslanspivak.com/lsbasi-part17/>)

Author: Ruslan Spivak

Published: 2019-08-28T15:00:00Z

Content type: tutorial

Language: en

Sources: [Ruslan Spivak](<https://devfeed.tech/sources/ruslan-spivak.md>)

Topics: [function](<https://devfeed.tech/topics/function.md>), [data](<https://devfeed.tech/topics/data.md>), [Hardware](<https://devfeed.tech/topics/hardware.md>)

Tags: [blog](<https://devfeed.tech/tags/blog.md>), [build](<https://devfeed.tech/tags/build.md>), [function](<https://devfeed.tech/tags/function.md>), [hardware](<https://devfeed.tech/tags/hardware.md>), [implement](<https://devfeed.tech/tags/implement.md>), [memory](<https://devfeed.tech/tags/memory.md>), [series](<https://devfeed.tech/tags/series.md>), [simple](<https://devfeed.tech/tags/simple.md>), [values](<https://devfeed.tech/tags/values.md>), [variable](<https://devfeed.tech/tags/variable.md>)

## AI overview

Part 17 of a series on building an interpreter explains plans to implement a new memory system for programs, procedure calls, and function calls, replacing the GLOBAL_MEMORY dictionary. It introduces memory as a way to store and access data and distinguishes physical memory from interpreter-level storage by variable names.

## Source excerpt

You may have to fight a battle more than once to win it. - Margaret Thatcher