Why Predefined macros? - Purpose & Use Cases

The Big Idea

Discover how your code can tell you exactly where and when it runs without you lifting a finger!

The Scenario

Imagine writing a C program where you need to include the current date, time, or file name manually every time you compile or debug. You have to type these details yourself or update them each time you change the code.

The Problem

This manual method is slow and error-prone. You might forget to update the date or file name, leading to confusion during debugging. It also wastes time and makes your code less reliable.

The Solution

Predefined macros automatically provide useful information like the current file name, line number, compilation date, and time. This saves you from typing or updating these details manually, making your code smarter and easier to maintain.

Before vs After

✗ Before

#include <stdio.h>

int main() {
    printf("File: myfile.c\n");
    printf("Line: 10\n");
    return 0;
}

✓ After

#include <stdio.h>

int main() {
    printf("File: %s\n", __FILE__);
    printf("Line: %d\n", __LINE__);
    return 0;
}

What It Enables

It enables your program to automatically know and display important information about itself without extra effort.

Real Life Example

When debugging a program, predefined macros like __FILE__ and __LINE__ help you quickly find where an error happened without manually adding that info.

Key Takeaways

Predefined macros save time by automating code information.

They reduce errors caused by manual updates.

They make debugging and logging easier and more reliable.

Practice

1. Which of the following predefined macros in C gives the current line number in the source code?

easy

A. __LINE__

B. __FILE__

C. __DATE__

D. __TIME__

Solution

1. Step 1: Understand predefined macros purpose

   Predefined macros provide info about the code or environment automatically.

2. Step 2: Identify macro for line number

   __LINE__ gives the current line number in the source file.

3. Final Answer:

   __LINE__ -> Option A

4. Quick Check:

   Line number macro = __LINE__ [OK]

Hint: Line number macro always has LINE in its name [OK]

Common Mistakes:

• Confusing __FILE__ with line number
• Using __DATE__ or __TIME__ for line info
• Thinking __LINE__ is a function

2. Which of the following is the correct syntax to print the current file name using a predefined macro in C?

easy

A. printf("File: %s", FILE);

B. printf("File: %s", __FILE__);

C. printf("File: %s", _FILE_);

D. printf("File: %s", file);

Solution

1. Step 1: Recall predefined macro for file name

   The macro __FILE__ holds the current source file name as a string.

2. Step 2: Check correct syntax usage

   Using printf("File: %s", __FILE__); correctly prints the file name.

3. Final Answer:

   printf("File: %s", __FILE__); -> Option B

4. Quick Check:

   File name macro syntax = __FILE__ [OK]

Hint: Predefined macros always have double underscores before and after [OK]

Common Mistakes:

• Omitting underscores in __FILE__
• Using FILE without underscores
• Using lowercase file instead of macro

3. What will be the output of the following C code snippet?

#include <stdio.h>
int main() {
    printf("Date: %s\n", __DATE__);
    printf("Time: %s\n", __TIME__);
    return 0;
}

medium

A. Compilation error due to undefined macros

B. Date: __DATE__\nTime: __TIME__

C. Date: current date at compilation\nTime: current time at compilation

D. Date: 0000-00-00\nTime: 00:00:00

Solution

1. Step 1: Understand __DATE__ and __TIME__ macros

   These macros expand to strings representing the date and time when the code was compiled.

2. Step 2: Predict output of printf statements

   The program prints the compilation date and time as strings, not the macro names or errors.

3. Final Answer:

   Date: current date at compilation\nTime: current time at compilation -> Option C

4. Quick Check:

   __DATE__ and __TIME__ show compile date/time [OK]

Hint: __DATE__ and __TIME__ show compile time info as strings [OK]

Common Mistakes:

• Expecting runtime current date/time
• Thinking macros print their own names
• Assuming macros are undefined

4. Consider this C code snippet:

#include <stdio.h>
int main() {
    printf("Line: %d\n", LINE);
    return 0;
}

What is the problem with this code?

medium

A. LINE is not a predefined macro; it should be __LINE__

B. Missing semicolon after printf

C. printf format specifier %d is incorrect for LINE

D. No problem; code runs fine

Solution

1. Step 1: Identify the macro usage error

   The code uses LINE instead of the correct predefined macro __LINE__.

2. Step 2: Understand consequences

   Since LINE is undefined, this causes a compilation error.

3. Final Answer:

   LINE is not a predefined macro; it should be __LINE__ -> Option A

4. Quick Check:

   Predefined macros need double underscores [OK]

Hint: Predefined macros always have double underscores before and after [OK]

Common Mistakes:

• Using LINE without underscores
• Thinking %d is wrong for line number
• Ignoring missing macro error

5. You want to log the current file name, line number, and compilation date in your C program for debugging. Which code snippet correctly uses predefined macros to do this?

hard

A. printf("File: %s, Line: %d, Date: %s\n", _FILE_, _LINE_, _DATE_);

B. printf("File: %s, Line: %d, Date: %s\n", FILE, LINE, DATE);

C. printf("File: %s, Line: %d, Date: %s\n", "__FILE__", "__LINE__", "__DATE__");

D. printf("File: %s, Line: %d, Date: %s\n", __FILE__, __LINE__, __DATE__);

Solution

1. Step 1: Identify correct predefined macros

   The macros __FILE__, __LINE__, and __DATE__ provide file name, line number, and compile date respectively.

2. Step 2: Check correct usage in printf

   Using them directly without quotes and with correct underscores prints the desired info.

3. Final Answer:

   printf("File: %s, Line: %d, Date: %s\n", __FILE__, __LINE__, __DATE__); -> Option D

4. Quick Check:

   Use double underscore macros directly in printf [OK]

Hint: Use __FILE__, __LINE__, __DATE__ directly without quotes [OK]

Common Mistakes:

• Using macros without underscores
• Putting macros inside quotes (prints names, not values)
• Using single underscores instead of double