Why file handling is required in C - Challenge Your Understanding

Challenge - 5 Problems

🧠 Conceptual

intermediate

Why do programs need file handling?

Why is file handling important in programming?

A To store data permanently so it can be used later even after the program stops running.

B To make the program run faster by using files instead of memory.

C To allow programs to communicate directly with the computer's hardware.

D To prevent the program from using any memory during execution.

💡 Hint

Think about what happens to data when a program closes.

File handling lets programs save data permanently on disk, so it is not lost when the program ends. This is why it is important.

❓ Predict Output

intermediate

Output of file handling code snippet

What will be the output of this C code?

C

#include <stdio.h>
int main() {
    FILE *fp = fopen("test.txt", "w");
    if (fp == NULL) {
        printf("Error opening file\n");
        return 1;
    }
    fprintf(fp, "Hello World\n");
    fclose(fp);
    printf("File written successfully\n");
    return 0;
}

A File written successfully

B Error opening file

C Hello World

D No output

💡 Hint

Look at what is printed to the screen, not what is written inside the file.

The program writes "Hello World" to the file but prints "File written successfully" to the screen.

❓ Predict Output

advanced

What error does this file handling code raise?

What error will this C code produce when run?

C

#include <stdio.h>
int main() {
    FILE *fp = fopen("nonexistent.txt", "r");
    char buffer[20];
    fgets(buffer, 20, fp);
    printf("%s", buffer);
    fclose(fp);
    return 0;
}

A File not found error printed automatically

B Compilation error

C No error, prints file content

D Segmentation fault (runtime error)

💡 Hint

What happens if fopen fails and returns NULL, then you use that pointer?

If fopen fails to open the file, fp is NULL. Using fgets on NULL causes a segmentation fault (runtime crash).

🧠 Conceptual

advanced

Why is file handling needed for large data?

Why do programs use file handling when working with large amounts of data?

A Because files make the program run faster than memory.

B Because large data cannot fit entirely in memory and must be stored on disk.

C Because file handling automatically compresses large data.

D Because files are easier to edit than memory.

💡 Hint

Think about the limits of computer memory versus disk storage.

Memory is limited and temporary. Large data is stored in files on disk to handle more data than memory can hold.

🚀 Application

expert

What is the value of variable 'count' after this code runs?

Consider this C code that counts lines in a file. What is the value of count after running?

C

#include <stdio.h>
int main() {
    FILE *fp = fopen("data.txt", "r");
    int count = 0;
    char ch;
    if (fp == NULL) return 1;
    while ((ch = fgetc(fp)) != EOF) {
        if (ch == '\n') count++;
    }
    fclose(fp);
    printf("%d\n", count);
    return 0;
}

A Number of words in data.txt

B Number of characters in data.txt

C Number of newline characters in data.txt

D Always zero

💡 Hint

Look at what the code counts inside the loop.

The code counts how many newline characters '\n' appear in the file, which equals the number of lines.

Practice

1. Why is file handling required in C programming?

easy

A. To use more memory during execution

B. To make the program run faster

C. To save data permanently outside the program

D. To avoid using variables

Solution

1. Step 1: Understand the purpose of file handling

   File handling allows programs to store data permanently on disk, beyond the program's runtime.

2. Step 2: Compare options with this purpose

   Only saving data permanently matches the main reason for file handling; other options are unrelated.

3. Final Answer:

   To save data permanently outside the program -> Option C

4. Quick Check:

   File handling = permanent data storage [OK]

Hint: File handling = saving data permanently [OK]

Common Mistakes:

• Thinking file handling speeds up program
• Confusing memory use with file storage
• Believing file handling avoids variables

2. Which of the following is the correct way to open a file for writing in C?

easy

A. FILE fp = fopen("data.txt", "w");

B. FILE *fp = fopen("data.txt", "r");

C. FILE *fp = open("data.txt", "w");

D. FILE *fp = fopen("data.txt", "w");

Solution

1. Step 1: Recall fopen syntax in C

   fopen requires a FILE pointer and mode string; "w" mode opens file for writing.

2. Step 2: Check each option

   FILE *fp = fopen("data.txt", "w"); uses FILE *fp and fopen with "w" correctly; others have wrong function, mode, or variable type.

3. Final Answer:

   FILE *fp = fopen("data.txt", "w"); -> Option D

4. Quick Check:

   Open file for writing = fopen with "w" [OK]

Hint: Use fopen with "w" mode and FILE pointer [OK]

Common Mistakes:

• Using 'r' mode to write
• Using open() instead of fopen()
• Declaring FILE variable instead of pointer

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

FILE *fp = fopen("test.txt", "w");
fprintf(fp, "Hello World");
fclose(fp);
fp = fopen("test.txt", "r");
char str[20];
fgets(str, 20, fp);
printf("%s", str);
fclose(fp);

medium

A. Compilation error

B. Hello World

C. No output

D. Runtime error

Solution

1. Step 1: Write and close file

   The code opens "test.txt" for writing, writes "Hello World", then closes the file.

2. Step 2: Open file for reading and read content

   It reopens the file for reading, reads the string into str, and prints it.

3. Final Answer:

   Hello World -> Option B

4. Quick Check:

   Write then read file prints saved text [OK]

Hint: Write, close, reopen, read to get output [OK]

Common Mistakes:

• Forgetting to close file before reading
• Using wrong mode for fopen
• Not reading file content before printing

4. Identify the error in this C code for file handling:

FILE *fp;
fp = fopen("data.txt", "r");
fprintf(fp, "Test");
fclose(fp);

medium

A. Using fprintf on a file opened in read mode

B. Not closing the file

C. Missing file pointer declaration

D. Using wrong filename

Solution

1. Step 1: Check file open mode

   The file is opened in "r" mode, which is read-only.

2. Step 2: Check usage of fprintf

   fprintf writes to file, but writing is not allowed in read mode, causing error.

3. Final Answer:

   Using fprintf on a file opened in read mode -> Option A

4. Quick Check:

   Write requires "w" mode, not "r" [OK]

Hint: Write only on files opened with "w" or "a" [OK]

Common Mistakes:

• Writing to read-only file
• Ignoring file open mode
• Not checking fopen return value

5. You want to save user input permanently and add new entries without deleting old data. Which file mode should you use in C?

hard

A. "a" (append mode)

B. "r" (read mode)

C. "w" (write mode)

D. "r+" (read and write mode)

Solution

1. Step 1: Understand file modes

   "w" overwrites file, "r" reads only, "a" appends data at end, "r+" reads and writes but does not append.

2. Step 2: Choose mode for adding without deleting

   Append mode "a" adds new data without deleting existing content.

3. Final Answer:

   "a" (append mode) -> Option A

4. Quick Check:

   Append mode = add data without deleting [OK]

Hint: Use "a" mode to add data without erasing [OK]

Common Mistakes:

• Using "w" which erases old data
• Confusing "r+" with append mode
• Trying to write in "r" mode