Why file handling is required in C - Performance Analysis

Time Complexity: Why file handling is required

O(n)

Understanding Time Complexity

We want to understand how the time to run file handling operations changes as the size of the file grows.

How does reading or writing more data affect the time it takes?

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

#include <stdio.h>

int main() {
    FILE *file = fopen("data.txt", "r");
    int ch;
    while ((ch = fgetc(file)) != EOF) {
        putchar(ch);
    }
    fclose(file);
    return 0;
}
    

This code reads a file character by character and prints it to the screen.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: Reading each character from the file one by one.
• How many times: Once for every character in the file until the end.

How Execution Grows With Input

As the file size grows, the program reads more characters, so it takes more time.

Input Size (characters)	Approx. Operations
10	About 10 reads
100	About 100 reads
1000	About 1000 reads

Pattern observation: The time grows directly with the number of characters in the file.

Final Time Complexity

Time Complexity: O(n)

This means the time to read the file grows in a straight line with the file size.

Common Mistake

[X] Wrong: "Reading a file always takes the same time no matter how big it is."

[OK] Correct: The program reads each character one by one, so bigger files take more time.

Interview Connect

Understanding how file size affects reading time helps you write efficient programs that handle data well.

Self-Check

"What if we read the file in larger chunks instead of one character at a time? How would the time complexity change?"

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