File pointers in C - Step-by-Step Execution

Concept Flow - File pointers

Open file with fopen()

↓

Get FILE* pointer

↓

Use pointer with fread()/fwrite()/fprintf()/fscanf()

↓

Move pointer with fseek()/rewind()

↓

Read/write data

↓

Close file with fclose()

↓

End

Open a file to get a pointer, use it to read/write or move inside the file, then close it.

Execution Sample

C

#include <stdio.h>

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

This code opens a file for writing, writes "Hello" with a newline, then closes the file.

Execution Table

Step	Action	FILE* pointer value	Result/Output
1	Call fopen("test.txt", "w")	fp -> valid FILE pointer	File "test.txt" opened for writing
2	Call fprintf(fp, "Hello\n")	fp unchanged	Writes "Hello\n" to file
3	Call fclose(fp)	fp invalid after close	File closed, resources freed
4	Return 0 from main	N/A	Program ends successfully

💡 File closed and program ends normally

Variable Tracker

Variable	Start	After fopen	After fprintf	After fclose	Final
fp	NULL	Valid FILE pointer	Valid FILE pointer	Invalid (closed)	Invalid (closed)

Key Moments - 3 Insights

Why do we need to check if fopen returns NULL?

Because fopen returns NULL if the file cannot be opened (see step 1 in execution_table). Using a NULL pointer causes errors.

Does fprintf change the FILE* pointer value?

No, fprintf uses the pointer to write data but does not change the pointer itself (see step 2 in execution_table).

What happens if we forget to call fclose?

The file may not save data properly and resources stay allocated. fclose flushes buffers and frees resources (see step 3).

Visual Quiz - 3 Questions

Look at the execution_table, what is the value of fp after fopen is called?

A An integer

B A valid FILE pointer

C NULL

D Undefined

💡 Hint

Check step 1 in execution_table under 'FILE* pointer value'

At which step does the file get closed?

A Step 1

B Step 2

C Step 3

D Step 4

💡 Hint

Look for fclose call in execution_table

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

A Check if pointer is NULL and handle error

B Proceed to write data anyway

C Call fclose immediately

D Ignore and continue

💡 Hint

Refer to key_moments about checking fopen return value

Concept Snapshot

File pointers in C:
- Use fopen() to open a file and get FILE* pointer
- Use fprintf(), fscanf(), fread(), fwrite() with FILE* to read/write
- Use fseek(), rewind() to move pointer inside file
- Always check if fopen returns NULL before use
- Close file with fclose() to save and free resources

Full Transcript

In C, file pointers are used to work with files. First, you open a file using fopen(), which returns a FILE* pointer. This pointer is like a handle to the file. You use this pointer with functions like fprintf() to write or fscanf() to read. You can move the pointer inside the file with fseek() or rewind(). After finishing, you close the file with fclose() to save changes and free resources. Always check if fopen returns NULL to avoid errors. This example opens a file named "test.txt" for writing, writes "Hello" with a newline, then closes the file properly.

Practice

1. What does a file pointer in C represent?

easy

A. A variable that stores file contents

B. A reference to a file opened in the program

C. A function to read files

D. A type of file format

Solution

1. Step 1: Understand what a file pointer is

   A file pointer is a special pointer that points to a file stream opened by the program.

2. Step 2: Differentiate from other options

   It is not the file contents or a function, but a reference to the file for reading or writing.

3. Final Answer:

   A reference to a file opened in the program -> Option B

4. Quick Check:

   File pointer = Reference to opened file [OK]

Hint: File pointer points to file stream, not contents [OK]

Common Mistakes:

• Thinking file pointer stores file data
• Confusing file pointer with file reading function
• Assuming file pointer is a file format

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

easy

A. FILE *fp = fopen("file.txt", "r");

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

C. fopen FILE *fp = "file.txt", "r";

D. FILE *fp = open("file.txt", "r");

Solution

1. Step 1: Recall fopen syntax

   The fopen function returns a pointer to FILE, so the variable must be FILE *fp.

2. Step 2: Check each option

   FILE *fp = fopen("file.txt", "r"); correctly declares FILE *fp and calls fopen with filename and mode "r".

3. Final Answer:

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

4. Quick Check:

   Correct fopen syntax = FILE *fp = fopen("file.txt", "r"); [OK]

Hint: fopen returns FILE pointer, so use FILE * variable [OK]

Common Mistakes:

• Declaring FILE variable instead of pointer
• Using open() instead of fopen()
• Incorrect order of fopen parameters

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

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

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

medium

A. Hello\n

B. Compilation error

C. test.txt

D. Hello

Solution

1. Step 1: Write and close file

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

2. Step 2: Read and print file content

   It reopens test.txt for reading, reads a line into buffer, then prints it. fgets reads until newline or buffer limit.

3. Final Answer:

   Hello (printed as Hello with newline) -> Option D

4. Quick Check:

   File write/read prints "Hello" [OK]

Hint: fgets reads line including newline, printf prints it [OK]

Common Mistakes:

• Expecting literal \n printed
• Confusing fprintf and printf output
• Forgetting to close file before reopening

4. Identify the error in this code snippet:

FILE *fp;
fp = fopen("data.txt", "r");
char c = fgetc(fp);
while (c != EOF) {
    putchar(c);
    c = fgetc(fp);
}
fclose(fp);

medium

A. fgetc returns int, not char, causing wrong EOF check

B. fopen mode "r" is incorrect for reading

C. Missing fclose call

D. putchar cannot print characters

Solution

1. Step 1: Check fgetc return type

   fgetc returns int to allow EOF (-1) detection, storing in char loses EOF info.

2. Step 2: Understand EOF check failure

   Comparing char c to EOF fails because c cannot hold EOF value properly, causing infinite loop or wrong output.

3. Final Answer:

   fgetc returns int, not char, causing wrong EOF check -> Option A

4. Quick Check:

   Use int for fgetc result to detect EOF [OK]

Hint: Store fgetc result in int to detect EOF correctly [OK]

Common Mistakes:

• Using char instead of int for fgetc result
• Ignoring EOF check causing infinite loops
• Assuming putchar can't print chars

5. You want to append text "World" to an existing file "hello.txt" without deleting its content. Which is the correct way to open the file?

hard

A. FILE *fp = fopen("hello.txt", "r");

B. FILE *fp = fopen("hello.txt", "w");

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

D. FILE *fp = fopen("hello.txt", "r+");

Solution

1. Step 1: Understand file modes

   "a" mode opens file for appending, preserving existing content and writing at the end.

2. Step 2: Compare other modes

   "w" overwrites file, "r" is read-only, "r+" allows read/write but does not append automatically.

3. Final Answer:

   FILE *fp = fopen("hello.txt", "a"); -> Option C

4. Quick Check:

   Append mode = "a" [OK]

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

Common Mistakes:

• Using "w" which erases file content
• Using "r" which is read-only
• Confusing "r+" with append mode