File modes in C - Step-by-Step Execution

Concept Flow - File modes

Start

↓

Open file with mode

↓

Check if file opened

↓

Read/Write/Append

↓

Close file

↓

End

Open a file with a mode, check success, perform actions, then close the file.

Execution Sample

C

#include <stdio.h>

int main() {
  FILE *f = fopen("test.txt", "w");
  if (f == NULL) {
    perror("Failed to open file");
    return 1;
  }
  fprintf(f, "Hello\n");
  fclose(f);
  return 0;
}

Open a file for writing, write 'Hello' and close the file.

Execution Table

Step	Action	File Pointer (f)	Result/Output
1	Call fopen("test.txt", "w")	Non-NULL (file opened)	File opened for writing
2	Call fprintf(f, "Hello\n")	Non-NULL	Writes 'Hello' to file
3	Call fclose(f)	Non-NULL before close	File closed
4	Return 0	Pointer value unchanged	Program ends

💡 Program ends after closing the file and returning 0

Variable Tracker

Variable	Start	After fopen	After fprintf	After fclose	Final
f	undefined	pointer to file	pointer to file	pointer to file (closed)	pointer to file (closed)

Key Moments - 3 Insights

Why do we check if fopen returns NULL?

Because fopen returns NULL if the file cannot be opened (see step 1 in execution_table). Checking prevents errors when using the file pointer.

What happens if we write to a file opened in "r" mode?

Writing fails because "r" mode opens the file for reading only. The program may crash or produce errors if writing is attempted.

Why must we call fclose after finishing with the file?

fclose releases system resources and ensures data is saved properly (see step 3 in execution_table). Not closing can cause data loss or resource leaks.

Visual Quiz - 3 Questions

Look at the execution_table, what is the value of 'f' after calling fclose?

A NULL

B Pointer to file

C Undefined

D Integer 0

💡 Hint

Check the 'File Pointer (f)' column at step 3 and 4 in execution_table

At which step does the program write 'Hello' to the file?

A Step 1

B Step 3

C Step 2

D Step 4

💡 Hint

Look at the 'Action' and 'Result/Output' columns in execution_table

If fopen fails and returns NULL, what should the program do before using the file pointer?

A Check if the pointer is NULL and handle the error

B Close the file immediately

C Proceed to write to the file

D Ignore and continue

💡 Hint

Refer to key_moments about checking fopen return value

Concept Snapshot

File modes in C control how files are opened:
"r" = read only
"w" = write (create or overwrite)
"a" = append (write at end)
Always check fopen returns NULL before use.
Use fclose to close files and save data.

Full Transcript

This example shows how to open a file in C using fopen with mode "w" to write. The program checks if the file opened successfully by verifying the file pointer is not NULL. Then it writes the string "Hello" to the file using fprintf. After writing, it closes the file with fclose to save changes and free resources. The execution table traces each step: opening the file, writing, closing, and ending the program. The variable tracker shows how the file pointer changes from undefined to a valid pointer, then remains the same after closing (fclose does not set the pointer to NULL). Key moments explain why checking fopen's return is important, why writing to a read-only file is invalid, and why fclose is necessary. The quiz tests understanding of file pointer states and error handling. The snapshot summarizes file modes and best practices for file handling in C.