C file input/output

Overview

This library uses what are called streams to operate with physical devices such as keyboards, printers, terminals or with any other type of files supported by the system. Streams are an abstraction to interact with these in a uniform way. All streams have similar properties independent of the individual characteristics of the physical media they are associated with.

Functions

Most of the C file input/output functions are defined in (or in the C++ header , which contains the standard C functionality but in the namespace).

Constants

Constants defined in the header include:

Variables

Variables defined in the header include:

Member types

Data types defined in the header include:

• – also known as a file handlefile handle or a ** pointer**, this is an opaque pointer containing the information about a file or text stream needed to perform input or output operations on it, including:
• platform-specific identifier of the associated I/O device, such as a file descriptor
• the buffer
• stream orientation indicator (unset, narrow, or wide)
• stream buffering state indicator (unbuffered, line buffered, fully buffered)
• I/O mode indicator (input stream, output stream, or update stream)
• binary/text mode indicator
• end-of-file indicator
• error indicator
• the current stream position and multibyte conversion state (an object of type )
• reentrant lock (required as of C11)
• – a non-array type capable of uniquely identifying the position of every byte in a file and every conversion state that can occur in all supported multibyte character encodings
• – an unsigned integer type which is the type of the result of the operator.

Extensions{{anchor|POSIX}}

The POSIX standard defines several extensions to in its Base Definitions, among which are a function that allocates memory, the and functions that establish the link between objects and file descriptors, and a group of functions for creating objects that refer to in-memory buffers.

Example

The following C program opens a binary file called , reads five bytes from it, and then closes the file.

#include <stdio.h>
#include <stdlib.h>

int main(void) {
    char buffer[5];
    size_t len;
    FILE* fp = fopen("myfile", "rb");

    if (fp == NULL) {
        perror("Failed to open file \"myfile\"");
        return EXIT_FAILURE;
    }

    if ((len = fread(buffer, 1, 5, fp)) < 0) {
        fclose(fp);
        fputs("An error occurred while reading the file.\n", stderr);
        return EXIT_FAILURE;
    }

    fclose(fp);

    printf("The bytes read were: ");
    for (int i = 0; i < len; ++i) {
        printf("%02X ", buffer[i]);
    }
    putchar('\n');

    return EXIT_SUCCESS;
}

Alternatives to stdio{{anchor|Sfio}}

Several alternatives to have been developed. Among these are C++ I/O headers and, part of the C++ Standard Library. ISO C++ still requires the functionality, and it is found under header ``.

Other alternatives include the Sfio (A Safe/Fast I/O Library) library from AT&T Bell Laboratories. This library, introduced in 1991, aimed to avoid inconsistencies, unsafe practices and inefficiencies in the design of . Among its features is the possibility to insert callback functions into a stream to customize the handling of data read from or written to the stream. It was released to the outside world in 1997, and the last official stable release was 2005-02-01

References

References

1. "ISO/IEC 9899:1999 specification".
2. (1984). "[[The UNIX Programming Environment]]". [[Prentice Hall]].
3. (1987). "A Research Unix reader: annotated excerpts from the Programmer's Manual, 1971–1986".
4. "(stdio.h) - C++ Reference".
5. {{man. bd. stdio.h. SUS
6. "Sfio: A Safe/Fast I/O Library".
7. (1991). "SFIO: Safe/Fast String/File IO".
8. (2000). "Extended Formatting with Sfio".
9. "sfio Software Download Package List".
10. [https://github.com/lichray/sfio sfio-2005-02-01]
11. [https://github.com/att/ast/tree/master/src/lib/libast/sfio sfio-AST-2012-08-01]