4.1.3. Unit Objectives

You will be able to describe the concept of modular programming which uses a procedure of a function.

The first objective focuses on understanding what modular programming is. Modular programming involves breaking down a program into smaller, manageable pieces or modules, called procedures or functions. Each function serves a specific purpose, allowing programmers to organize and structure their code more efficiently. This approach enhances readability and maintainability, as well as allowing code reuse across different parts of a program. For instance, if you have a function that calculates the square of a number, you can call this function multiple times throughout your program without rewriting the logic.

Think of modular programming like building with LEGO blocks. Each block represents a function that has a specific role, such as adding a wheel to a car or creating the car body. By using different blocks (functions), you can build complex structures easily, and if you need to change or fix something, you only need to change one block instead of rebuilding the entire model.

You will be able to comprehend and discuss the basic requirements of CPU organization for a call function, including what registers and stacks are required.

The second objective aims to deepen your understanding of how a CPU handles function calls. Whenever a function is called, the CPU must save certain information about the current execution state—this includes the program counter (PC), which tracks the next instruction to execute, and the registers used during the execution. Moreover, a stack is crucial because it helps keep track of function calls, storing the context for each call. This allows the CPU to return to the correct location in the main program after the function execution is complete.

Imagine a chef who is cooking several dishes at once. The chef (CPU) has a main recipe (main program) and various note cards (function calls) for each dish. When the chef starts a new dish, they write down the current page of the recipe on a note card and move to the new dish. When the dish is done, they refer to the note card (stack) to remember where they left off in the main recipe. This way, they can manage multiple tasks without forgetting the steps needed for the main dish.

You will be able to design and explain the design issues of return and call instructions, such as how to design call instructions, return instructions, and which registers and stacks are involved.

The synthesis objective is about applying the knowledge gained. You'll learn how to design the call and return instructions used in programming. This includes understanding how to handle the stack for saving information about the function calls and managing the registers that hold data and status flags. The design issues may involve ensuring that the return address is saved properly in the stack so that execution can resume seamlessly after a function finishes. Additionally, it looks at the implications of nested function calls, where one function calls another, and how these layers impact how the stack is managed.

Consider a multi-level manager in a company. Each manager (function) can delegate tasks to their team (sub-functions). When a team completes a task, they must report back to their manager (return) to summarize progress (context). The lead manager needs to keep track of each team’s reports to make a final decision. This reflects how the CPU manages multiple function layers, requiring clear communication (call and return instructions) and a well-organized filing system (stack) to store all reports until they are needed.

--