The I/O functionality of C is fairly low-level by modern standards; C abstracts all file operations into operations on streams of bytes, which may be "input streams" or "output streams". Unlike some earlier programming languages, C has no direct support for random-access data files; to read from a record in the middle of a file, the programmer must create a stream, seek to the middle of the file, and then read bytes in sequence from the stream.
The stream model of file I/O was popularized by Unix, which was developed concurrently with the C programming language itself. The vast majority of modern operating systems have inherited streams from Unix, and many languages in the C programming language family have inherited C's file I/O interface with few if any changes (for example, PHP).
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.[4]
Functions
Most of the C file input/output functions are defined in <stdio.h> (or in the C++ header cstdio, which contains the standard C functionality but in the stdnamespace).
An integer which is the size of the buffer used by the setbuf() function
FILENAME_MAX
The size of a char array which is large enough to store the name of any file that can be opened
FOPEN_MAX
The number of files that may be open simultaneously; will be at least eight
_IOFBF
An abbreviation for "input/output fully buffered"; it is an integer which may be passed to the setvbuf() function to request block buffered input and output for an open stream
_IOLBF
An abbreviation for "input/output line buffered"; it is an integer which may be passed to the setvbuf() function to request line buffered input and output for an open stream
_IONBF
An abbreviation for "input/output not buffered"; it is an integer which may be passed to the setvbuf() function to request unbuffered input and output for an open stream
L_tmpnam
The size of a char array which is large enough to store a temporary filename generated by the tmpnam() function
NULL
A macro expanding to the null pointer constant; that is, a constant representing a pointer value which is guaranteed not to be a valid address of an object in memory
SEEK_CUR
An integer which may be passed to the fseek() function to request positioning relative to the current file position
SEEK_END
An integer which may be passed to the fseek() function to request positioning relative to the end of the file
SEEK_SET
An integer which may be passed to the fseek() function to request positioning relative to the beginning of the file
TMP_MAX
The maximum number of unique filenames generable by the tmpnam() function; will be at least 25
Variables
Variables defined in the <stdio.h> header include:
A pointer to a FILE which refers to the standard error stream, often a display terminal.
Member types
Data types defined in the <stdio.h> header include:
FILE – also known as a file handle or a FILE 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 mbstate_t)
fpos_t – 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
size_t – an unsigned integer type which is the type of the result of the sizeof operator.
Extensions
The POSIX standard defines several extensions to stdio in its Base Definitions, among which are a readline function that allocates memory, the fileno and fdopen functions that establish the link between FILE objects and file descriptors, and a group of functions for creating FILE objects that refer to in-memory buffers.[5]
Example
The following C program opens a binary file called myfile, reads five bytes from it, and then closes the file.
#include<stdio.h>#include<stdlib.h>intmain(void){charbuffer[5];FILE*fp=fopen("myfile","rb");if(fp==NULL){perror("Failed to open file \"myfile\"");returnEXIT_FAILURE;}if(fread(buffer,1,5,fp)<5){fclose(fp);fputs("An error occurred while reading the file.\n",stderr);returnEXIT_FAILURE;}fclose(fp);printf("The bytes read were: ");for(inti=0;i<5;++i){printf("%02X ",buffer[i]);}putchar('\n');returnEXIT_SUCCESS;}
Several alternatives to stdio have been developed. Among these is the C++ iostream library, part of the ISO C++ standard. ISO C++ still requires the stdio functionality.
Other alternatives include the Sfio[6] (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 stdio. 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.[7] It was released to the outside world in 1997, and the last release was 1 February 2005.[8]