EMZETT.
Login

Emzett Wiki

dateien-lesen

Properties1
tagsglossar, programmierung

2 min read

Read Files

In short: Reading data from an existing file into a program — either all at once completely, or step by step (line by line or in blocks), in order to process even very large files without loading them entirely into working memory.

In more detail: For text files, many languages offer buffered reading helper classes (see BufferedReader), which are more efficient than individual, unbuffered read accesses. A common mistake is not correctly detecting the end of the file, thereby either losing data or triggering an exception when attempting to read past the end of the file.

In Depth

The choice between “load everything at once” and “read step by step” is one of the most important decisions in file processing:

# Load completely - simple, but memory-intensive for large files
with open("file.txt") as f:
    full_content = f.read()
 
# Line by line - constant memory requirement, no matter how large the file is
with open("file.txt") as f:
    for line in f:
        process(line)

For a 5 KB configuration file, the difference doesn’t matter. For a 50 GB log file, it decides whether the program works at all — loading it completely would try to load all 50 GB into working memory at once, which usually fails or massively slows down the system. Reading line by line (or more generally: block by block) always keeps only a small excerpt in memory, regardless of the file’s total size.

Internally, this is often combined with a buffer (see BufferedReader): instead of physically accessing the storage device on every single read (slow), the runtime environment reads larger blocks into an intermediate memory area at once and serves the program’s individual read requests from there — significantly faster, especially for many small read accesses in a row.

A common beginner mistake is handling the end of file (EOF) incorrectly: if an attempt is made to read past the end, some APIs return a special value (e.g. -1 or None), others throw an exception — you have to know which behaviour the language/library in use shows, otherwise either infinite loops (the exit condition is never reached) or unhandled crashes result.

See also: Files, BufferedReader

Graph View

Backlinks