Subprograms

Welcome to the World of Subprograms!

In this chapter, we are going to learn how to be "lazy" programmers—in a good way! Instead of writing the same code over and over again, we will learn how to wrap our code into neat little packages called subprograms. Don't worry if programming feels a bit like a puzzle right now; by the end of these notes, you’ll see how subprograms make everything much easier to manage!

Prerequisite Check: Before we start, just remember that a program is a list of instructions for a computer. A subprogram is simply a smaller list of instructions stored inside the main program.

1. What are Subprograms?

A subprogram is a self-contained block of code that performs a specific task. Think of it like a "mini-program" inside your main code. In the Edexcel syllabus, you will see two main types: Procedures and Functions.

The "Pizza" Analogy

Imagine you are writing a massive recipe for a "Pizza Party." Instead of writing the instructions for "how to make dough" every time you mention a pizza, you could just write the dough instructions once in a separate box and call it MakeDough. Every time you need dough, you just point to that box! This is exactly how subprograms work.

Why do we use them? (The Benefits)

• Decomposition: It helps break a big, scary problem into smaller, manageable chunks.
• Reusability: You write the code once and use it many times.
• Easier Testing: You can test one small subprogram to make sure it works before putting it in the main program.
• Readability: It makes your code look cleaner and easier for humans to read.

Quick Review: Why use subprograms? To save time, reduce errors, and make code easier to read!

2. Procedures vs. Functions

This is a very important distinction for your exam. While they look similar, they have one major difference.

Procedures

A procedure is a subprogram that performs a specific task but does not send a value back to the main program. It just "does its job."
Example: A subprogram that clears the screen or prints a specific welcome message.

Functions

A function is a subprogram that performs a task and must return a value back to the part of the code that called it. It "gives something back."
Example: A subprogram that calculates the square root of a number and gives you the answer.

Memory Aid: Functions Find a value! (They Return it).

Common Mistake: Forgetting that a function must have a return statement. If it doesn't return anything, it's actually a procedure!

3. Parameters and Arguments

Sometimes, a subprogram needs information to do its job. If you have a subprogram called CalculateArea, it needs to know the length and width of the shape.

• Parameters: These are the "placeholders" defined in the subprogram. They are like empty slots waiting to be filled.
• Arguments: These are the actual values you pass into those slots when you call the subprogram.

Step-by-Step Example:
1. You define a function: function calculate(number1, number2). Here, number1 and number2 are parameters.
2. You call the function: calculate(10, 5). Here, 10 and 5 are arguments.

Takeaway: Parameters are the "labels" in the definition; Arguments are the "real data" used during the run.

4. Local and Global Variables

This is about "Scope"—which basically means "Where can I see this variable?"

Local Variables

A local variable is declared inside a subprogram. It only exists while that subprogram is running. Once the subprogram finishes, the variable is "deleted."
Analogy: Your house keys are "local" to your house. They don't work anywhere else, and nobody outside knows they exist.

Global Variables

A global variable is declared outside of all subprograms, usually at the very top of the script. It can be seen and used by any part of the program.
Analogy: The sun is "global." Everyone can see it, no matter which "subprogram" (house) they are in.

Did you know? It is generally better to use local variables. If you use too many global variables, one subprogram might accidentally change a value that another subprogram is using, causing a "logic error"!

5. Built-in vs. User-Devised Subprograms

You don't always have to write subprograms from scratch!

• Built-in Subprograms: These are already provided by the programming language (like Python). Examples include print(), input(), and len().
• Library Subprograms: These are sets of pre-written subprograms you can "import." For example, the math library gives you access to math.sqrt().
• User-Devised Subprograms: These are the ones you write to solve your specific problem.

Quick Review Box:
- Procedure: Does a task, no return value.
- Function: Does a task, returns a value.
- Scope: Local (inside) vs Global (outside).
- Single Entry/Exit: A good subprogram should start at the top and have one clear way out!

Summary Checklist

Before you move on, make sure you can answer these:
1. Can I explain the benefit of using a subprogram? (Decomposition/Reusability)
2. Do I know why a function is different from a procedure? (The Return value)
3. Can I identify a parameter in a piece of code?
4. Do I understand why a local variable is "safer" than a global one?

Don't worry if this seems tricky at first! Subprograms are like Lego bricks—once you learn how to snap them together, you can build much bigger and cooler programs!