Macro with arguments - Time & Space Complexity

Time Complexity: Macro with arguments

O(n)

Understanding Time Complexity

We want to see how the time it takes to run code with macros that have arguments changes as input grows.

How does using a macro with arguments affect the number of steps the program does?

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

#include <stdio.h>

#define SQUARE(x) ((x) * (x))

int main() {
    int n = 5;
    for (int i = 0; i < n; i++) {
        printf("%d\n", SQUARE(i));
    }
    return 0;
}

This code uses a macro with an argument to calculate the square of numbers from 0 to n-1 and prints them.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: The for-loop runs n times, calling the macro each time.
• How many times: The macro expands and runs once per loop iteration, so n times.

How Execution Grows With Input

Each time n grows, the loop runs more times, and the macro runs that many times too.

Input Size (n)	Approx. Operations
10	About 10 squares calculated and printed
100	About 100 squares calculated and printed
1000	About 1000 squares calculated and printed

Pattern observation: The work grows directly with n; doubling n doubles the work.

Final Time Complexity

Time Complexity: O(n)

This means the time to run grows in a straight line as the input size increases.

Common Mistake

[X] Wrong: "Macros with arguments run only once, so they don't affect time complexity."

[OK] Correct: Each time the macro is used in code, it expands and runs, so if inside a loop, it runs multiple times.

Interview Connect

Understanding how macros with arguments behave helps you explain how code runs and grows, a useful skill for writing efficient programs.

Self-Check

"What if we replaced the macro with a function call? How would the time complexity change?"

Practice

1. What does a macro with arguments in C do?

easy

A. It replaces code snippets with given values before compilation

B. It creates a new function at runtime

C. It allocates memory dynamically

D. It executes code conditionally during runtime

Solution

1. Step 1: Understand macro replacement

   Macros with arguments are replaced by the preprocessor before the program runs, substituting the macro call with the code snippet using the given arguments.

2. Step 2: Differentiate from functions

   Unlike functions, macros do not create executable code at runtime but perform textual substitution during compilation.

3. Final Answer:

   It replaces code snippets with given values before compilation -> Option A

4. Quick Check:

   Macro = code substitution before compile [OK]

Hint: Macros replace code before running, not at runtime [OK]

Common Mistakes:

• Thinking macros create functions
• Confusing macros with runtime code
• Assuming macros allocate memory

2. Which of the following is the correct syntax for defining a macro with two arguments a and b that adds them?

easy

A. #define ADD(a, b) a + b

B. #define ADD a, b (a + b)

C. #define ADD(a, b) (a + b)

D. #define ADD(a, b) {a + b}

Solution

1. Step 1: Check macro argument syntax

   Macro arguments must be enclosed in parentheses immediately after the macro name, like ADD(a, b).

2. Step 2: Ensure proper expression grouping

   To avoid operator precedence issues, the expression should be enclosed in parentheses: (a + b).

3. Final Answer:

   #define ADD(a, b) (a + b) -> Option C

4. Quick Check:

   Correct macro syntax = #define NAME(args) (expression) [OK]

Hint: Always put parentheses around macro arguments and whole expression [OK]

Common Mistakes:

• Missing parentheses around arguments
• Not enclosing expression in parentheses
• Using braces {} instead of parentheses

3. Given the macro definition #define SQUARE(x) x * x, what is the output of printf("%d", SQUARE(3 + 1));?

medium

A. Error

B. 16

C. 12

D. 7

Solution

1. Step 1: Expand the macro with argument

   The macro call SQUARE(3 + 1) expands to 3 + 1 * 3 + 1 because the macro definition lacks parentheses around the expression.

2. Step 2: Apply operator precedence

   Multiplication has higher precedence, so 3 + (1 * 3) + 1 = 3 + 3 + 1 = 7.

3. Final Answer:

   7 -> Option D

4. Quick Check:

   Without parentheses, macro expands incorrectly = 7 [OK]

Hint: Without parentheses, macro args can cause wrong math [OK]

Common Mistakes:

• Assuming macro adds parentheses automatically
• Ignoring operator precedence
• Expecting 16 as square of 4

4. Identify the error in this macro definition: #define MULTIPLY(a, b) a * b)

medium

A. Extra closing parenthesis at the end

B. Missing opening parenthesis before a

C. Arguments should not have parentheses

D. Macro name should be lowercase

Solution

1. Step 1: Check parentheses balance

   The macro ends with an extra closing parenthesis ")" that does not match any opening parenthesis.

2. Step 2: Confirm correct macro syntax

   Macro should be defined as #define MULTIPLY(a, b) (a * b) with balanced parentheses around the expression.

3. Final Answer:

   Extra closing parenthesis at the end -> Option A

4. Quick Check:

   Parentheses must be balanced in macro definitions [OK]

Hint: Count parentheses carefully in macro definitions [OK]

Common Mistakes:

• Ignoring unmatched parentheses
• Thinking arguments can't have parentheses
• Believing macro names must be lowercase

5. You want to create a macro MAX(a, b) that returns the larger of two values. Which definition correctly handles expressions as arguments without errors?

hard

A. #define MAX(a, b) ((a > b) ? a : b)

B. #define MAX(a, b) ((a) > (b) ? (a) : (b))

C. #define MAX(a, b) a > b ? a : b

D. #define MAX(a, b) (a > b ? a : b)

Solution

1. Step 1: Understand argument safety

   To safely handle expressions as arguments, each argument must be enclosed in parentheses to avoid precedence errors.

2. Step 2: Check full macro expression grouping

   The entire conditional expression should be enclosed in parentheses to ensure correct evaluation when used in larger expressions.

3. Final Answer:

   #define MAX(a, b) ((a) > (b) ? (a) : (b)) -> Option B

4. Quick Check:

   Parentheses around args and whole expression prevent bugs [OK]

Hint: Always parenthesize macro args and whole expression [OK]

Common Mistakes:

• Missing parentheses around arguments
• Not enclosing entire expression
• Assuming macro works like a function