File modes in C - Time & Space Complexity

Time Complexity: File modes

O(n)

Understanding Time Complexity

When working with files in C, the mode you choose affects how the program reads or writes data.

We want to understand how the time to open and process a file changes as the file size grows.

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

FILE *file = fopen("data.txt", "r");
char buffer[256];

while (fgets(buffer, sizeof(buffer), file)) {
    // process the line
}
fclose(file);
    

This code opens a file in read mode and reads it line by line until the end.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: Reading each line from the file using fgets.
• How many times: Once for every line in the file until the end.

How Execution Grows With Input

As the file gets bigger, the program reads more lines, so it takes longer.

Input Size (lines)	Approx. Operations (reads)
10	10
100	100
1000	1000

Pattern observation: The number of operations grows directly with the number of lines in the file.

Final Time Complexity

Time Complexity: O(n)

This means the time to read the file grows linearly with the number of lines.

Common Mistake

[X] Wrong: "Opening a file is slow and depends on file size."

[OK] Correct: Opening a file is usually a quick operation; the time depends mostly on how much data you read or write, not just opening.

Interview Connect

Understanding how file reading scales helps you write efficient programs and answer questions about handling large data files.

Self-Check

"What if we changed the mode from reading line by line to reading the entire file at once? How would the time complexity change?"

Practice

1. Which file mode in C opens a file for reading only, without allowing any changes to the file?

easy

A. "w" mode

B. "r" mode

C. "a" mode

D. "rw" mode

Solution

1. Step 1: Understand file modes in C

   "r" mode opens a file for reading only, without modifying it.

2. Step 2: Compare other modes

   "w" mode opens for writing and clears the file; "a" mode appends; "rw" is invalid in C.

3. Final Answer:

   "r" mode -> Option B

4. Quick Check:

   Read-only mode = "r" [OK]

Hint: Read-only files use "r" mode in C [OK]

Common Mistakes:

• Confusing "w" with read mode
• Using "rw" which is invalid in C
• Thinking "a" allows reading

2. Which of the following is the correct syntax to open a file named data.txt for writing in C?

easy

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

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

C. FILE *fp = fopen("data.txt", "a");

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

Solution

1. Step 1: Identify correct function and mode

   In C, fopen opens files; "w" mode opens for writing.

2. Step 2: Check other options

   FILE *fp = fopen("data.txt", "r"); uses "r" (read), C uses "a" (append), D uses wrong function open.

3. Final Answer:

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

4. Quick Check:

   Write mode uses fopen with "w" [OK]

Hint: Use fopen with "w" to write files in C [OK]

Common Mistakes:

• Using open() instead of fopen()
• Confusing "r" with write mode
• Using "a" when write mode is needed

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

FILE *fp = fopen("test.txt", "w");
fputs("Hello", fp);
fclose(fp);

fp = fopen("test.txt", "a");
fputs(" World", fp);
fclose(fp);

fp = fopen("test.txt", "r");
char buffer[20];
fgets(buffer, 20, fp);
printf("%s", buffer);
fclose(fp);

medium

A. Hello

B. Error

C. Hello World

D. World

Solution

1. Step 1: Write "Hello" to file with "w" mode

   Opening with "w" clears file and writes "Hello".

2. Step 2: Append " World" with "a" mode

   Opening with "a" adds " World" at the end without erasing.

3. Step 3: Read file content with "r" mode

   Reading file returns "Hello World" in buffer.

4. Final Answer:

   Hello World -> Option C

5. Quick Check:

   Write + Append + Read = "Hello World" [OK]

Hint: "w" clears file, "a" adds at end, reading shows combined text [OK]

Common Mistakes:

• Assuming "a" overwrites file
• Forgetting "w" clears file
• Expecting only "Hello" output

4. Identify the error in this C code snippet that tries to open a file for appending:

FILE *fp;
fp = fopen("log.txt", "wa");
if (fp == NULL) {
    printf("Failed to open file\n");
}

medium

A. Incorrect file mode string "wa"

B. Missing fclose(fp) after opening

C. Using printf instead of perror

D. File name should be absolute path

Solution

1. Step 1: Check file mode string validity

   "wa" is not a valid mode; modes must be "r", "w", "a" or with "b" for binary.

2. Step 2: Understand consequences

   Invalid mode causes fopen to fail and return NULL.

3. Final Answer:

   Incorrect file mode string "wa" -> Option A

4. Quick Check:

   File modes must be valid strings like "a" or "w" [OK]

Hint: File modes are single valid strings like "r", "w", or "a" [OK]

Common Mistakes:

• Combining modes incorrectly like "wa"
• Ignoring fopen failure check
• Assuming "wa" means write and append

5. You want to create a log file that preserves old logs and adds new entries each time your program runs. Which file mode should you use in C to open the file, and why?

hard

A. "w" mode, because it clears old logs and writes fresh data

B. "r" mode, because it reads existing logs before adding new ones

C. "r+" mode, because it allows reading and writing at the start

D. "a" mode, because it appends new logs preserving old content

Solution

1. Step 1: Understand log file requirements

   Logs must keep old entries and add new ones without erasing.

2. Step 2: Match file mode to requirement

   "a" mode appends data at the end, preserving existing content.

3. Step 3: Evaluate other modes

   "w" clears file, "r" only reads, "r+" reads/writes but doesn't append automatically.

4. Final Answer:

   "a" mode, because it appends new logs preserving old content -> Option D

5. Quick Check:

   Append mode "a" preserves and adds data [OK]

Hint: Use "a" mode to add without deleting old file content [OK]

Common Mistakes:

• Using "w" which erases old logs
• Thinking "r" can write
• Confusing "r+" with append mode