Define macro - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ Predict Output

intermediate

What is the output of this macro usage?

Consider the following C code using a macro. What will be printed when this program runs?

C

#include <stdio.h>
#define SQUARE(x) x * x

int main() {
    int a = 3;
    printf("%d\n", SQUARE(a + 1));
    return 0;
}

A 16

B 7

C Error: macro expansion invalid

D 10

💡 Hint

Remember how macros expand without parentheses around parameters.

The macro expands to a + 1 * a + 1. With a=3, due to operator precedence (* before +), it evaluates to 3 + (1 * 3) + 1 = 3 + 3 + 1 = 7.

❓ Predict Output

intermediate

What is the output of this corrected macro?

Now consider this corrected macro definition. What will be printed?

C

#include <stdio.h>
#define SQUARE(x) ((x) * (x))

int main() {
    int a = 3;
    printf("%d\n", SQUARE(a + 1));
    return 0;
}

A Error: macro expansion invalid

B 10

C 16

D 7

💡 Hint

Parentheses in macros help control the order of operations.

The macro expands to ((a + 1) * (a + 1)) which is (4 * 4) = 16.

❓ Predict Output

advanced

What is the output of this macro with side effects?

Look at this code using a macro that doubles a value. What will be printed?

C

#include <stdio.h>
#define DOUBLE(x) ((x) + (x))

int main() {
    int i = 2;
    printf("%d\n", DOUBLE(i++));
    return 0;
}

A Undefined behavior or unexpected result

B 5

C 4

D 6

💡 Hint

Macros can cause expressions to be evaluated multiple times.

The macro expands to ((i++) + (i++)), so i++ is evaluated twice, causing side effects and undefined or unexpected results.

🧠 Conceptual

advanced

What does this macro do?

Given the macro below, what is its purpose?

C

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

A Returns the sum of a and b

B Returns the smaller of a and b

C Returns true if a equals b

D Returns the larger of a and b

💡 Hint

Look at the conditional operator ? :

The macro compares a and b and returns the one that is greater.

🔧 Debug

expert

Why does this macro cause a compilation error?

Examine the macro and code below. Why does it cause a compilation error?

C

#define INCREMENT(x) x++

int main() {
    int a = 5;
    int b = INCREMENT(a) * 2;
    return 0;
}

A Because macro expansion lacks parentheses causing wrong operator precedence

B Because x++ cannot be used inside macros

C Because the macro is missing a semicolon

D Because multiplication operator * is invalid here

💡 Hint

Think about how the macro expands and operator precedence.

The macro expands to a++ * 2 which is parsed as (a++) * 2, but without parentheses around x++, it can cause unexpected behavior or warnings. The main issue is lack of parentheses causing operator precedence problems.

Practice

1. What does the #define directive do in C?

easy

A. It creates a macro that replaces text before compilation.

B. It declares a variable with a fixed value.

C. It defines a function that runs at runtime.

D. It allocates memory for a constant.

Solution

1. Step 1: Understand the purpose of #define

   The #define directive tells the compiler to replace all occurrences of a name with a given value or code snippet before the program runs.

2. Step 2: Differentiate from variables and functions

   Unlike variables or functions, macros do not allocate memory or run at runtime; they are simple text replacements done before compilation.

3. Final Answer:

   It creates a macro that replaces text before compilation. -> Option A

4. Quick Check:

   #define = text replacement [OK]

Hint: Macros replace text before running code [OK]

Common Mistakes:

• Thinking macros allocate memory
• Confusing macros with functions
• Assuming macros run at runtime

2. Which of the following is the correct syntax to define a macro named PI with value 3.14?

easy

A. #define PI 3.14

B. #define PI = 3.14

C. define PI 3.14

D. #define(PI, 3.14)

Solution

1. Step 1: Recall correct #define syntax

   The correct syntax is #define NAME value without an equal sign or parentheses.

2. Step 2: Check each option

   #define PI = 3.14 uses an equal sign which is incorrect. define PI 3.14 misses the #. #define(PI, 3.14) uses parentheses incorrectly. Only #define PI 3.14 matches the correct syntax.

3. Final Answer:

   #define PI 3.14 -> Option A

4. Quick Check:

   Correct macro syntax = #define NAME value [OK]

Hint: No equal sign in macro definitions [OK]

Common Mistakes:

• Adding '=' sign after macro name
• Omitting '#' in #define
• Using parentheses like a function

3. What is the output of this C code?

#include <stdio.h>
#define SQUARE(x) ((x) * (x))

int main() {
    int a = 3;
    printf("%d", SQUARE(a + 1));
    return 0;
}

medium

A. Error

B. 7

C. 10

D. 16

Solution

1. Step 1: Expand the macro with argument

   The macro call SQUARE(a + 1) expands to ((a + 1) * (a + 1)).

2. Step 2: Calculate the expression

   Substitute a = 3: ((3 + 1) * (3 + 1)) = (4 * 4) = 16.

3. Final Answer:

   16 -> Option D

4. Quick Check:

   Macro expansion and calculation = 16 [OK]

Hint: Remember to expand macros fully before calculating [OK]

Common Mistakes:

• Not using parentheses in macro causing wrong order
• Calculating as 3 + 1 * 3 + 1 = 7
• Assuming macro is a function call

4. Identify the error in this macro definition:

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

medium

A. Macro names cannot have parameters

B. Incorrect use of ? operator

C. Missing parentheses around the entire macro expression

D. Missing semicolon at the end

Solution

1. Step 1: Analyze macro expression grouping

   The macro expands to a > b ? a : b without parentheses, which can cause wrong evaluation when used in expressions.

2. Step 2: Understand importance of parentheses

   Wrapping the entire macro in parentheses like ((a) > (b) ? (a) : (b)) ensures correct order and prevents bugs.

3. Final Answer:

   Missing parentheses around the entire macro expression -> Option C

4. Quick Check:

   Always parenthesize macro expressions [OK]

Hint: Wrap macro expressions in parentheses to avoid errors [OK]

Common Mistakes:

• Not using parentheses around macro body
• Assuming macros behave like functions
• Adding semicolon inside macro definition

5. You want to create a macro MIN that returns the smaller of two values x and y. Which of the following is the best macro definition to avoid common bugs?

hard

A. #define MIN(x, y) ((x < y) ? x : y)

B. #define MIN(x, y) ((x) < (y) ? (x) : (y))

C. #define MIN(x, y) (x < y ? x : y)

D. #define MIN(x, y) x < y ? x : y

Solution

1. Step 1: Check for parentheses around parameters

   #define MIN(x, y) ((x) < (y) ? (x) : (y)) wraps each parameter in parentheses to avoid issues when arguments are expressions.

2. Step 2: Check for parentheses around entire expression

   #define MIN(x, y) ((x) < (y) ? (x) : (y)) also wraps the whole expression in parentheses to ensure correct evaluation in larger expressions.

3. Step 3: Compare with other options

   Options A, B, and C miss some parentheses, risking wrong results or precedence bugs.

4. Final Answer:

   #define MIN(x, y) ((x) < (y) ? (x) : (y)) -> Option B

5. Quick Check:

   Parenthesize parameters and expression in macros [OK]

Hint: Always parenthesize macro parameters and full expression [OK]

Common Mistakes:

• Missing parentheses around parameters
• Missing parentheses around entire macro
• Assuming macros behave like functions