Why modular programming is needed in C - Challenge Your Understanding

Challenge - 5 Problems

🧠 Conceptual

intermediate

Why use modular programming in C?

Which of the following is the main reason to use modular programming in C?

A To make the program run faster by using fewer CPU cycles

B To write all code in a single file for simplicity

C To avoid using variables and functions altogether

D To organize code into separate parts that are easier to understand and maintain

💡 Hint

Think about how breaking a big task into smaller pieces helps in real life.

Modular programming helps by dividing code into smaller, manageable parts. This makes it easier to read, fix, and reuse code.

❓ Predict Output

intermediate

Output of modular code with separate functions

What is the output of this C program?

C

#include <stdio.h>

void greet() {
    printf("Hello, ");
}

void name() {
    printf("World!\n");
}

int main() {
    greet();
    name();
    return 0;
}

A Hello,World!

B Hello, World!

C Hello World!

D

Hello
World!

💡 Hint

Look carefully at the spaces and newline characters in the print statements.

The greet function prints "Hello, " with a space and no newline. The name function prints "World!" with a newline. Together they print "Hello, World!" on one line.

🔧 Debug

advanced

Identify the error in modular code

What error will this C code produce?

C

#include <stdio.h>

void printMessage();

int main() {
    printMessage();
    return 0;
}

void printMessage() {
    printf("Modular programming is useful\n");
}

A Linker error: undefined reference to printMessage

B Syntax error: missing semicolon after function declaration

C No error, program runs and prints the message

D Runtime error: segmentation fault

💡 Hint

Check if the function is declared and defined properly.

The function printMessage is declared before main and defined after main. This is valid in C, so the program runs without error and prints the message.

📝 Syntax

advanced

Correct syntax for splitting code into modules

Which option shows the correct way to declare and define a function in separate files for modular programming?

A In header file: <code>void greet();</code> In source file: <code>void greet() { printf("Hi\n"); }</code>

B In header file: <code>void greet() { printf("Hi\n"); }</code> In source file: <code>void greet();</code>

C In header file: <code>void greet() { printf("Hi\n"); }</code> In source file: <code>void greet() { printf("Hi\n"); }</code>

D In header file: <code>void greet;</code> In source file: <code>void greet() { printf("Hi\n"); }</code>

💡 Hint

Think about what belongs in a header file versus a source file.

The header file should only declare the function prototype (no body). The source file defines the function with its body.

🚀 Application

expert

Number of modules needed for a program

You are writing a C program that reads user input, processes data, and prints results. To follow modular programming principles, how many separate modules should you create at minimum?

A Three modules: one for input, one for processing, one for output

B Two modules: one for input and output, one for processing

C Four modules: one for input, one for processing, one for output, one for main function

D One module containing all code

💡 Hint

Think about separating different tasks into clear parts.

Separating input, processing, and output into three modules makes the program easier to maintain and understand. The main function can be part of one of these or separate, but minimum three modules are best practice.