C# How to Read From a Text File

General-purpose programming language

C
Major implementations
The C Programming Language ^[1] (often referred to equally K&R), the seminal book on C
Paradigm	Multi-epitome: imperative (procedural), structured
Designed by	Dennis Ritchie
Developer	Dennis Ritchie & Bong Labs (creators); ANSI X3J11 (ANSI C); ISO/IEC JTC1/SC22/WG14 (ISO C)
First appeared	1972; 50 years ago (1972) ^[2]

Stable release	C17 / June 2018; iii years ago (2018-06)
Preview release	C2x (N2731) / October 18, 2021; 4 months ago (2021-ten-18) ^[three]

Typing discipline	Static, weak, manifest, nominal
OS	Cross-platform
Filename extensions	.c, .h
Website	www.iso.org/standard/74528.html www.open up-std.org/jtc1/sc22/wg14/
pcc, GCC, Clang, Intel C, C++Builder, Microsoft Visual C++, Watcom C
Dialects
Cyclone, Unified Parallel C, Split up-C, Cilk, C*
Influenced by
B (BCPL, CPL), ALGOL 68,^[iv] assembly, PL/I, FORTRAN
Influenced
Numerous: AMPL, AWK, csh, C++, C--, C#, Objective-C, D, Go, Java, JavaScript, JS++, Julia, Limbo, LPC, Perl, PHP, Pike, Processing, Python, Band,^[five]Rust, Seed7, Vala, Verilog (HDL),^[6] Nim, Zig
C Programming at Wikibooks

C (, every bit in the letter c) is a general-purpose, procedural estimator programming linguistic communication supporting structured programming, lexical variable scope, and recursion, with a static type organization. By design, C provides constructs that map efficiently to typical car instructions. It has found lasting utilize in applications previously coded in assembly language. Such applications include operating systems and various application software for reckoner architectures that range from supercomputers to PLCs and embedded systems.

A successor to the programming language B, C was originally developed at Bell Labs by Dennis Ritchie between 1972 and 1973 to construct utilities running on Unix. It was applied to re-implementing the kernel of the Unix operating system.^[7] During the 1980s, C gradually gained popularity. It has get one of the well-nigh widely used programming languages,^[8] ^[9] with C compilers from various vendors available for the majority of existing computer architectures and operating systems. C has been standardized by ANSI since 1989 (ANSI C) and by the International Organization for Standardization (ISO).

C is an imperative procedural language. It was designed to be compiled to provide depression-level admission to memory and language constructs that map efficiently to motorcar instructions, all with minimal runtime support. Despite its depression-level capabilities, the linguistic communication was designed to encourage cross-platform programming. A standards-compliant C program written with portability in mind can be compiled for a broad variety of figurer platforms and operating systems with few changes to its source code.^[10]

Since 2000, C has consistently ranked among the top 2 languages in the TIOBE alphabetize, a measure of the popularity of programming languages.^[11]

Overview [edit]

Similar most procedural languages in the ALGOL tradition, C has facilities for structured programming and allows lexical variable telescopic and recursion. Its static type system prevents unintended operations. In C, all executable code is contained inside subroutines (too called "functions", though non strictly in the sense of functional programming). Function parameters are always passed past value (except arrays). Pass-by-reference is fake in C by explicitly passing pointer values. C program source text is gratuitous-format, using the semicolon every bit a statement terminator and curly braces for grouping blocks of statements.

The C linguistic communication also exhibits the post-obit characteristics:

The language has a pocket-size, stock-still number of keywords, including a full set of control menstruum primitives: if/else, for, do/while, while, and switch. User-defined names are not distinguished from keywords by any kind of sigil.
It has a large number of arithmetic, bitwise, and logic operators: +,+=,++,&,||, etc.
More than ane consignment may be performed in a unmarried statement.
Functions:
- Function return values tin exist ignored, when not needed.
- Function and data pointers permit ad hoc run-time polymorphism.
- Functions may not be divers within the lexical scope of other functions.
Data typing is static, only weakly enforced; all information has a type, but implicit conversions are possible.
Declaration syntax mimics usage context. C has no "ascertain" keyword; instead, a statement beginning with the proper name of a type is taken equally a declaration. In that location is no "function" keyword; instead, a function is indicated by the presence of a parenthesized argument listing.
User-defined (typedef) and compound types are possible.
- Heterogeneous amass data types (struct) let related data elements to exist accessed and assigned equally a unit.
- Wedlock is a structure with overlapping members; but the concluding fellow member stored is valid.
- Array indexing is a secondary notation, divers in terms of pointer arithmetic. Unlike structs, arrays are non first-class objects: they cannot be assigned or compared using single congenital-in operators. There is no "array" keyword in use or definition; instead, square brackets signal arrays syntactically, for example calendar month[11].
- Enumerated types are possible with the enum keyword. They are freely interconvertible with integers.
- Strings are not a distinct data type, but are conventionally implemented equally nix-terminated character arrays.
Low-level admission to estimator memory is possible by converting machine addresses to typed pointers.
Procedures (subroutines not returning values) are a special case of role, with an untyped render blazon void.
A preprocessor performs macro definition, source code file inclusion, and provisional compilation.
There is a basic class of modularity: files can be compiled separately and linked together, with control over which functions and data objects are visible to other files via static and extern attributes.
Circuitous functionality such every bit I/O, string manipulation, and mathematical functions are consistently delegated to library routines.

While C does not include sure features constitute in other languages (such every bit object orientation and garbage collection), these can exist implemented or emulated, frequently through the employ of external libraries (e.yard., the GLib Object System or the Boehm garbage collector).

Relations to other languages [edit]

Many later languages accept borrowed directly or indirectly from C, including C++, C#, Unix'south C shell, D, Go, Java, JavaScript (including transpilers), Julia, Limbo, LPC, Objective-C, Perl, PHP, Python, Ruby, Rust, Swift, Verilog and SystemVerilog (hardware description languages).^[6] These languages have fatigued many of their command structures and other basic features from C. Nigh of them (Python being a dramatic exception) also express highly similar syntax to C, and they tend to combine the recognizable expression and statement syntax of C with underlying type systems, data models, and semantics that can be radically dissimilar.

History [edit]

Early on developments [edit]

Timeline of language development
Year	C Standard^[10]
1972	Nascency
1978	K&R C
1989/1990	ANSI C and ISO C
1999	C99
2011	C11
2017	C17
TBD	C2x

The origin of C is closely tied to the development of the Unix operating system, originally implemented in associates language on a PDP-7 by Dennis Ritchie and Ken Thompson, incorporating several ideas from colleagues. Somewhen, they decided to port the operating system to a PDP-11. The original PDP-xi version of Unix was also developed in assembly language.^[7]

Thompson desired a programming language to make utilities for the new platform. At start, he tried to make a Fortran compiler, only soon gave upwardly the thought. Instead, he created a cut-down version of the recently adult BCPL systems programming language. The official description of BCPL was non available at the time,^[12] and Thompson modified the syntax to be less wordy, producing the similar but somewhat simpler B.^[vii] Notwithstanding, few utilities were ultimately written in B because information technology was also boring, and B could not accept advantage of PDP-11 features such equally byte addressability.

In 1972, Ritchie started to meliorate B, most notably adding information typing for variables, which resulted in creating a new language C.^[13] The C compiler and some utilities made with it were included in Version 2 Unix.^[14]

At Version 4 Unix, released in November 1973, the Unix kernel was extensively re-implemented in C.^[vii] By this fourth dimension, the C language had acquired some powerful features such as struct types.

The preprocessor was introduced around 1973 at the urging of Alan Snyder and too in recognition of the usefulness of the file-inclusion mechanisms available in BCPL and PL/I. Its original version provided simply included files and simple string replacements: #include and #define of parameterless macros. Shortly later that, information technology was extended, mostly by Mike Lesk and and then by John Reiser, to incorporate macros with arguments and conditional compilation.^[7]

Unix was 1 of the first operating organization kernels implemented in a language other than assembly. Earlier instances include the Multics system (which was written in PL/I) and Master Control Program (MCP) for the Burroughs B5000 (which was written in ALGOL) in 1961. In around 1977, Ritchie and Stephen C. Johnson made farther changes to the linguistic communication to facilitate portability of the Unix operating system. Johnson's Portable C Compiler served equally the basis for several implementations of C on new platforms.^[thirteen]

K&R C [edit]

In 1978, Brian Kernighan and Dennis Ritchie published the first edition of The C Programming Language.^[1] This book, known to C programmers as Thou&R, served for many years equally an informal specification of the language. The version of C that information technology describes is ordinarily referred to as "K&R C". As this was released in 1978, it is also referred to as C78.^[fifteen] The second edition of the book^[xvi] covers the later on ANSI C standard, described below.

One thousand&R introduced several language features:

Standard I/O library
long int data type
unsigned int data type
Chemical compound assignment operators of the form =op (such as =-) were changed to the form op= (that is, -=) to remove the semantic ambiguity created by constructs such as i=-ten, which had been interpreted every bit i =- 10 (decrement i by 10) instead of the possibly intended i = -10 (let i exist −10).

Even subsequently the publication of the 1989 ANSI standard, for many years K&R C was still considered the "lowest common denominator" to which C programmers restricted themselves when maximum portability was desired, since many older compilers were still in utilise, and because carefully written K&R C lawmaking tin be legal Standard C as well.

In early versions of C, only functions that render types other than int must be declared if used before the function definition; functions used without prior declaration were presumed to render type int.

For example:

                        long                                    some_function            ();                        /* int */                                    other_function            ();                        /* int */                                    calling_function            ()                        {                                                long                                    test1            ;                                                register                                    /* int */                                    test2            ;                                                test1                                    =                                    some_function            ();                                                if                                    (            test1                                    >                                    1            )                                                test2                                    =                                    0            ;                                                else                                                test2                                    =                                    other_function            ();                                                return                                    test2            ;                        }

The int type specifiers which are commented out could exist omitted in K&R C, merely are required in later on standards.

Since K&R role declarations did not include any information about office arguments, part parameter type checks were not performed, although some compilers would upshot a alert message if a local function was called with the wrong number of arguments, or if multiple calls to an external office used different numbers or types of arguments. Dissever tools such every bit Unix's lint utility were developed that (among other things) could check for consistency of function use across multiple source files.

In the years following the publication of M&R C, several features were added to the linguistic communication, supported past compilers from AT&T (in particular PCC^[17]) and some other vendors. These included:

void functions (i.e., functions with no return value)
functions returning struct or marriage types (rather than pointers)
consignment for struct information types
enumerated types

The large number of extensions and lack of agreement on a standard library, together with the language popularity and the fact that non even the Unix compilers precisely implemented the Yard&R specification, led to the necessity of standardization.

ANSI C and ISO C [edit]

During the late 1970s and 1980s, versions of C were implemented for a wide variety of mainframe computers, minicomputers, and microcomputers, including the IBM PC, as its popularity began to increase significantly.

In 1983, the American National Standards Institute (ANSI) formed a committee, X3J11, to establish a standard specification of C. X3J11 based the C standard on the Unix implementation; however, the not-portable portion of the Unix C library was handed off to the IEEE working grouping 1003 to become the ground for the 1988 POSIX standard. In 1989, the C standard was ratified as ANSI X3.159-1989 "Programming Language C". This version of the language is often referred to as ANSI C, Standard C, or sometimes C89.

In 1990, the ANSI C standard (with formatting changes) was adopted by the International System for Standardization (ISO) as ISO/IEC 9899:1990, which is sometimes called C90. Therefore, the terms "C89" and "C90" refer to the same programming linguistic communication.

ANSI, like other national standards bodies, no longer develops the C standard independently, just defers to the international C standard, maintained by the working group ISO/IEC JTC1/SC22/WG14. National adoption of an update to the international standard typically occurs inside a year of ISO publication.

One of the aims of the C standardization procedure was to produce a superset of G&R C, incorporating many of the afterwards introduced unofficial features. The standards committee also included several additional features such as part prototypes (borrowed from C++), void pointers, support for international grapheme sets and locales, and preprocessor enhancements. Although the syntax for parameter declarations was augmented to include the style used in C++, the K&R interface continued to be permitted, for compatibility with existing source code.

C89 is supported past electric current C compilers, and nigh modern C code is based on information technology. Any plan written merely in Standard C and without whatsoever hardware-dependent assumptions volition run correctly on whatever platform with a conforming C implementation, inside its resource limits. Without such precautions, programs may compile but on a certain platform or with a item compiler, due, for example, to the utilize of non-standard libraries, such as GUI libraries, or to a reliance on compiler- or platform-specific attributes such as the verbal size of data types and byte endianness.

In cases where code must be compilable by either standard-conforming or K&R C-based compilers, the __STDC__ macro tin exist used to split the code into Standard and Chiliad&R sections to prevent the use on a 1000&R C-based compiler of features bachelor just in Standard C.

After the ANSI/ISO standardization process, the C language specification remained relatively static for several years. In 1995, Normative Amendment 1 to the 1990 C standard (ISO/IEC 9899/AMD1:1995, known informally every bit C95) was published, to right some details and to add more than extensive back up for international character sets.^[eighteen]

C99 [edit]

The C standard was further revised in the late 1990s, leading to the publication of ISO/IEC 9899:1999 in 1999, which is normally referred to every bit "C99". It has since been amended three times past Technical Corrigenda.^[xix]

C99 introduced several new features, including inline functions, several new information types (including long long int and a complex type to represent complex numbers), variable-length arrays and flexible array members, improved support for IEEE 754 floating indicate, support for variadic macros (macros of variable arity), and support for ane-line comments offset with //, every bit in BCPL or C++. Many of these had already been implemented as extensions in several C compilers.

C99 is for the most part astern compatible with C90, but is stricter in some ways; in detail, a declaration that lacks a type specifier no longer has int implicitly causeless. A standard macro __STDC_VERSION__ is divers with value 199901L to point that C99 support is bachelor. GCC, Solaris Studio, and other C compilers now support many or all of the new features of C99. The C compiler in Microsoft Visual C++, all the same, implements the C89 standard and those parts of C99 that are required for compatibility with C++eleven.^[20] ^{[ needs update ]}

In addition, support for Unicode identifiers (variable / office names) in the form of escaped characters (e.g. \U0001f431) is now required. Back up for raw Unicode names is optional.

C11 [edit]

In 2007, work began on another revision of the C standard, informally called "C1X" until its official publication on 2011-12-08. The C standards committee adopted guidelines to limit the adoption of new features that had not been tested past existing implementations.

The C11 standard adds numerous new features to C and the library, including type generic macros, anonymous structures, improved Unicode support, atomic operations, multi-threading, and premises-checked functions. It also makes some portions of the existing C99 library optional, and improves compatibility with C++. The standard macro __STDC_VERSION__ is defined as 201112L to indicate that C11 support is bachelor.

C17 [edit]

Published in June 2018, C17 is the electric current standard for the C programming language. Information technology introduces no new language features, only technical corrections, and clarifications to defects in C11. The standard macro __STDC_VERSION__ is defined every bit 201710L.

C2x [edit]

C2x is an informal name for the next (after C17) major C language standard revision. It is expected to be voted on in 2023 and would therefore exist called C23.^[21] ^{[ better source needed ]}

Embedded C [edit]

Historically, embedded C programming requires nonstandard extensions to the C language in club to back up exotic features such as fixed-point arithmetics, multiple distinct retention banks, and bones I/O operations.

In 2008, the C Standards Commission published a technical study extending the C language^[22] to accost these issues by providing a common standard for all implementations to attach to. Information technology includes a number of features not available in normal C, such equally fixed-betoken arithmetic, named address spaces, and basic I/O hardware addressing.

Syntax [edit]

C has a formal grammar specified by the C standard.^[23] Line endings are generally non pregnant in C; however, line boundaries practise have significance during the preprocessing phase. Comments may appear either betwixt the delimiters /* and */, or (since C99) post-obit // until the finish of the line. Comments delimited past /* and */ do not nest, and these sequences of characters are non interpreted equally comment delimiters if they announced inside string or character literals.^[24]

C source files incorporate declarations and function definitions. Function definitions, in turn, contain declarations and statements. Declarations either ascertain new types using keywords such as struct, matrimony, and enum, or assign types to and perchance reserve storage for new variables, ordinarily by writing the type followed by the variable name. Keywords such as char and int specify born types. Sections of lawmaking are enclosed in braces ({ and }, sometimes chosen "curly brackets") to limit the telescopic of declarations and to act equally a single statement for control structures.

As an imperative language, C uses statements to specify deportment. The most common statement is an expression argument, consisting of an expression to be evaluated, followed past a semicolon; as a side result of the evaluation, functions may be chosen and variables may exist assigned new values. To modify the normal sequential execution of statements, C provides several control-flow statements identified by reserved keywords. Structured programming is supported by if … [else] conditional execution and past do … while, while, and for iterative execution (looping). The for statement has separate initialization, testing, and reinitialization expressions, whatever or all of which tin can be omitted. break and continue can be used to leave the innermost enclosing loop statement or skip to its reinitialization. In that location is also a not-structured goto statement which branches directly to the designated characterization inside the function. switch selects a case to be executed based on the value of an integer expression.

Expressions can use a variety of built-in operators and may contain office calls. The order in which arguments to functions and operands to nigh operators are evaluated is unspecified. The evaluations may fifty-fifty be interleaved. However, all side effects (including storage to variables) will occur before the next "sequence point"; sequence points include the end of each expression argument, and the entry to and return from each function call. Sequence points also occur during evaluation of expressions containing certain operators (&&, ||, ?: and the comma operator). This permits a high degree of object code optimization past the compiler, but requires C programmers to accept more care to obtain reliable results than is needed for other programming languages.

Kernighan and Ritchie say in the Introduction of The C Programming Language: "C, similar any other language, has its blemishes. Some of the operators accept the wrong precedence; some parts of the syntax could be amend."^[25] The C standard did not attempt to correct many of these blemishes, because of the touch on of such changes on already existing software.

Character set [edit]

The basic C source character prepare includes the following characters:

Lowercase and uppercase messages of ISO Basic Latin Alphabet: a–z A–Z
Decimal digits: 0–9
Graphic characters: ! " # % & ' ( ) * + , - . / : ; < = > ? [ \ ] ^ _ { | } ~
Whitespace characters: space, horizontal tab, vertical tab, grade feed, newline

Newline indicates the stop of a text line; it need not correspond to an actual single grapheme, although for convenience C treats it as one.

Additional multi-byte encoded characters may be used in string literals, but they are not entirely portable. The latest C standard (C11) allows multi-national Unicode characters to be embedded portably within C source text by using \uXXXX or \UXXXXXXXX encoding (where the X denotes a hexadecimal grapheme), although this feature is non yet widely implemented.

The basic C execution character set contains the same characters, along with representations for alert, backspace, and carriage return. Run-time back up for extended character sets has increased with each revision of the C standard.

Reserved words [edit]

C89 has 32 reserved words, likewise known every bit keywords, which are the words that cannot be used for any purposes other than those for which they are predefined:

automobile
break
case
char
const
continue
default
do
double
else
enum
extern
float
for
goto
if
int
long
annals
return
short
signed
sizeof
static
struct
switch
typedef
marriage
unsigned
void
volatile
while

C99 reserved 5 more words:

_Bool
_Complex
_Imaginary
inline
restrict

C11 reserved seven more words:^[26]

_Alignas
_Alignof
_Atomic
_Generic
_Noreturn
_Static_assert
_Thread_local

Nigh of the recently reserved words brainstorm with an underscore followed by a capital letter, because identifiers of that form were previously reserved by the C standard for use only by implementations. Since existing program source code should not have been using these identifiers, information technology would non be affected when C implementations started supporting these extensions to the programming language. Some standard headers do define more convenient synonyms for underscored identifiers. The language previously included a reserved discussion called entry, just this was seldom implemented, and has now been removed as a reserved word.^[27]

Operators [edit]

C supports a rich set of operators, which are symbols used within an expression to specify the manipulations to be performed while evaluating that expression. C has operators for:

arithmetic: +, -, *, /, %
consignment: =
augmented assignment: +=, -=, *=, /=, %=, &=, |=, ^=, <<=, >>=
bitwise logic: ~, &, |, ^
bitwise shifts: <<, >>
boolean logic: !, &&, ||
conditional evaluation: ? :
equality testing: ==, !=
calling functions: ( )
increase and decrement: ++, --
member selection: ., ->
object size: sizeof
order relations: <, <=, >, >=
reference and dereference: &, *, [ ]
sequencing: ,
subexpression grouping: ( )
type conversion: (typename)

C uses the operator = (used in mathematics to express equality) to bespeak assignment, post-obit the precedent of Fortran and PL/I, but unlike ALGOL and its derivatives. C uses the operator == to exam for equality. The similarity between these two operators (consignment and equality) may result in the accidental utilize of 1 in identify of the other, and in many cases, the mistake does not produce an error message (although some compilers produce warnings). For example, the conditional expression if (a == b + 1) might mistakenly be written as if (a = b + ane), which will exist evaluated equally true if a is not nothing afterwards the assignment.^[28]

The C operator precedence is not always intuitive. For example, the operator == binds more tightly than (is executed prior to) the operators & (bitwise AND) and | (bitwise OR) in expressions such as x & i == 0, which must exist written equally (x & 1) == 0 if that is the coder'south intent.^[29]

"Howdy, earth" example [edit]

The "hello, world" example, which appeared in the first edition of 1000&R, has become the model for an introductory programme in nigh programming textbooks. The program prints "hello, globe" to the standard output, which is unremarkably a terminal or screen brandish.

The original version was:^[30]

                        principal            ()                        {                                                printf            (            "hi, earth            \n            "            );                        }

A standard-conforming "hello, world" plan is:^[a]

                        #include                                    <stdio.h>                        int                                    primary            (            void            )                        {                                                printf            (            "hi, world            \n            "            );                        }

The starting time line of the program contains a preprocessing directive, indicated past #include. This causes the compiler to replace that line with the entire text of the stdio.h standard header, which contains declarations for standard input and output functions such equally printf and scanf. The angle brackets surrounding stdio.h indicate that stdio.h is located using a search strategy that prefers headers provided with the compiler to other headers having the same proper noun, as opposed to double quotes which typically include local or project-specific header files.

The adjacent line indicates that a function named main is being defined. The chief function serves a special purpose in C programs; the run-fourth dimension surroundings calls the main function to begin program execution. The type specifier int indicates that the value that is returned to the invoker (in this example the run-time environment) every bit a consequence of evaluating the main role, is an integer. The keyword void as a parameter list indicates that this function takes no arguments.^[b]

The opening curly brace indicates the offset of the definition of the main function.

The side by side line calls (diverts execution to) a role named printf, which in this case is supplied from a organisation library. In this call, the printf office is passed (provided with) a single argument, the address of the showtime character in the string literal "howdy, world\north". The string literal is an unnamed array with elements of blazon char, set up up automatically by the compiler with a last 0-valued character to mark the stop of the array (printf needs to know this). The \n is an escape sequence that C translates to a newline character, which on output signifies the finish of the current line. The return value of the printf function is of blazon int, only it is silently discarded since it is not used. (A more conscientious program might test the return value to determine whether or not the printf part succeeded.) The semicolon ; terminates the statement.

The endmost curly caryatid indicates the end of the lawmaking for the chief function. According to the C99 specification and newer, the main function, different any other function, volition implicitly render a value of 0 upon reaching the } that terminates the role. (Formerly an explicit return 0; statement was required.) This is interpreted by the run-time system every bit an exit lawmaking indicating successful execution.^[31]

Data types [edit]

The type system in C is static and weakly typed, which makes it similar to the type system of ALGOL descendants such as Pascal.^[32] At that place are built-in types for integers of diverse sizes, both signed and unsigned, floating-point numbers, and enumerated types (enum). Integer blazon char is oftentimes used for single-byte characters. C99 added a boolean datatype. At that place are also derived types including arrays, pointers, records (struct), and unions (union).

C is often used in low-level systems programming where escapes from the type system may be necessary. The compiler attempts to ensure type definiteness of most expressions, merely the developer can override the checks in various ways, either by using a type cast to explicitly catechumen a value from i blazon to another, or by using pointers or unions to reinterpret the underlying bits of a data object in another way.

Some find C's declaration syntax unintuitive, peculiarly for role pointers. (Ritchie's idea was to declare identifiers in contexts resembling their apply: "announcement reflects use".)^[33]

C'south usual arithmetic conversions let for efficient code to exist generated, but tin can sometimes produce unexpected results. For example, a comparing of signed and unsigned integers of equal width requires a conversion of the signed value to unsigned. This can generate unexpected results if the signed value is negative.

Pointers [edit]

C supports the employ of pointers, a type of reference that records the accost or location of an object or part in memory. Pointers tin be dereferenced to admission data stored at the address pointed to, or to invoke a pointed-to office. Pointers can be manipulated using consignment or pointer arithmetics. The run-time representation of a pointer value is typically a raw retentiveness address (perhaps augmented past an offset-within-word field), but since a pointer's type includes the type of the matter pointed to, expressions including pointers can exist type-checked at compile time. Arrow arithmetic is automatically scaled by the size of the pointed-to information type. Pointers are used for many purposes in C. Text strings are normally manipulated using pointers into arrays of characters. Dynamic retentivity allocation is performed using pointers. Many information types, such equally trees, are commonly implemented as dynamically allocated struct objects linked together using pointers. Pointers to functions are useful for passing functions as arguments to higher-order functions (such as qsort or bsearch) or as callbacks to be invoked by event handlers.^[31]

A nada pointer value explicitly points to no valid location. Dereferencing a nothing pointer value is undefined, often resulting in a sectionalization fault. Naught pointer values are useful for indicating special cases such as no "next" pointer in the concluding node of a linked list, or every bit an mistake indication from functions returning pointers. In appropriate contexts in source code, such equally for assigning to a pointer variable, a null arrow constant can exist written every bit 0, with or without explicit casting to a pointer type, or equally the NULL macro defined past several standard headers. In provisional contexts, null pointer values evaluate to fake, while all other arrow values evaluate to true.

Void pointers (void *) indicate to objects of unspecified type, and tin therefore be used every bit "generic" information pointers. Since the size and type of the pointed-to object is not known, void pointers cannot be dereferenced, nor is pointer arithmetic on them allowed, although they can hands be (and in many contexts implicitly are) converted to and from any other object arrow type.^[31]

Careless use of pointers is potentially dangerous. Because they are typically unchecked, a pointer variable can be fabricated to point to any arbitrary location, which can cause undesirable effects. Although properly used pointers bespeak to safe places, they can exist fabricated to betoken to dangerous places by using invalid arrow arithmetic; the objects they indicate to may go along to be used later deallocation (dangling pointers); they may exist used without having been initialized (wild pointers); or they may be directly assigned an unsafe value using a cast, union, or through another corrupt pointer. In general, C is permissive in allowing manipulation of and conversion between pointer types, although compilers typically provide options for various levels of checking. Another programming languages accost these problems by using more restrictive reference types.

Arrays [edit]

Assortment types in C are traditionally of a fixed, static size specified at compile time. The more recent C99 standard also allows a grade of variable-length arrays. However, it is also possible to classify a cake of memory (of arbitrary size) at run-time, using the standard library'south malloc function, and treat it equally an assortment.

Since arrays are always accessed (in effect) via pointers, array accesses are typically not checked against the underlying array size, although some compilers may provide bounds checking as an option.^[34] ^[35] Array bounds violations are therefore possible and tin can atomic number 82 to various repercussions, including illegal memory accesses, corruption of data, buffer overruns, and run-fourth dimension exceptions.

C does not have a special provision for declaring multi-dimensional arrays, merely rather relies on recursion within the blazon system to declare arrays of arrays, which effectively accomplishes the aforementioned thing. The index values of the resulting "multi-dimensional array" can be idea of equally increasing in row-major order. Multi-dimensional arrays are commonly used in numerical algorithms (mainly from applied linear algebra) to store matrices. The structure of the C array is well suited to this item task. Withal, in early on versions of C the premises of the array must be known fixed values or else explicitly passed to any subroutine that requires them, and dynamically sized arrays of arrays cannot be accessed using double indexing. (A workaround for this was to classify the array with an additional "row vector" of pointers to the columns.) C99 introduced "variable-length arrays" which accost this event.

The following instance using modern C (C99 or after) shows resource allotment of a two-dimensional array on the heap and the utilize of multi-dimensional array indexing for accesses (which can utilise premises-checking on many C compilers):

                        int                                    func            (            int                                    N            ,                                    int                                    M            )                        {                                                float                                    (            *            p            )[            N            ][            M            ]                                    =                                    malloc            (            sizeof                                    *            p            );                                                if                                    (            !            p            )                                                return                                    -1            ;                                                for                                    (            int                                    i                                    =                                    0            ;                                    i                                    <                                    Due north            ;                                    i            ++            )                                                for                                    (            int                                    j                                    =                                    0            ;                                    j                                    <                                    K            ;                                    j            ++            )                                                (            *            p            )[            i            ][            j            ]                                    =                                    i                                    +                                    j            ;                                                print_array            (            Northward            ,                                    1000            ,                                    p            );                                                free            (            p            );                                                return                                    1            ;                        }

Array–arrow interchangeability [edit]

The subscript note x[i] (where x designates a pointer) is syntactic saccharide for *(x+i).^[36] Taking advantage of the compiler's knowledge of the arrow type, the address that x + i points to is not the base of operations address (pointed to by ten) incremented by i bytes, but rather is divers to be the base of operations address incremented past i multiplied past the size of an element that x points to. Thus, ten[i] designates the i+1thursday element of the assortment.

Furthermore, in most expression contexts (a notable exception is equally operand of sizeof), an expression of array type is automatically converted to a pointer to the assortment'south first element. This implies that an array is never copied as a whole when named equally an argument to a function, just rather only the address of its offset element is passed. Therefore, although function calls in C use pass-by-value semantics, arrays are in result passed by reference.

The total size of an assortment x tin be adamant by applying sizeof to an expression of array blazon. The size of an element can be determined by applying the operator sizeof to any dereferenced chemical element of an assortment A, as in north = sizeof A[0]. This, the number of elements in a declared array A can be determined every bit sizeof A / sizeof A[0]. Note, that if only a pointer to the first chemical element is available as information technology is often the case in C code because of the automatic conversion described higher up, the data nearly the total blazon of the array and its length are lost.

Memory direction [edit]

One of the almost important functions of a programming language is to provide facilities for managing memory and the objects that are stored in retentiveness. C provides three distinct means to allocate memory for objects:^[31]

Static retentivity allocation: space for the object is provided in the binary at compile-time; these objects have an extent (or lifetime) equally long equally the binary which contains them is loaded into retentivity.
Automatic retention resource allotment: temporary objects tin can be stored on the stack, and this space is automatically freed and reusable after the block in which they are declared is exited.
Dynamic memory allocation: blocks of retentiveness of capricious size can exist requested at run-time using library functions such as malloc from a region of memory called the heap; these blocks persist until subsequently freed for reuse past calling the library function realloc or free

These three approaches are appropriate in dissimilar situations and have diverse trade-offs. For example, static memory allotment has picayune allocation overhead, automatic resource allotment may involve slightly more overhead, and dynamic memory allocation tin can potentially have a great deal of overhead for both allocation and deallocation. The persistent nature of static objects is useful for maintaining state information beyond function calls, automatic allocation is like shooting fish in a barrel to utilise only stack space is typically much more limited and transient than either static memory or heap infinite, and dynamic retentiveness allocation allows convenient allocation of objects whose size is known only at run-time. Most C programs make all-encompassing use of all three.

Where possible, automatic or static allocation is commonly simplest because the storage is managed past the compiler, freeing the programmer of the potentially error-decumbent chore of manually allocating and releasing storage. However, many data structures can change in size at runtime, and since static allocations (and automatic allocations earlier C99) must accept a stock-still size at compile-time, at that place are many situations in which dynamic resource allotment is necessary.^[31] Prior to the C99 standard, variable-sized arrays were a mutual case of this. (See the article on malloc for an example of dynamically allocated arrays.) Unlike automatic allotment, which can fail at run fourth dimension with uncontrolled consequences, the dynamic allocation functions return an indication (in the course of a naught pointer value) when the required storage cannot be allocated. (Static allocation that is too large is normally detected by the linker or loader, before the program can even begin execution.)

Unless otherwise specified, static objects incorporate zero or null pointer values upon programme startup. Automatically and dynamically allocated objects are initialized only if an initial value is explicitly specified; otherwise they initially have indeterminate values (typically, whatever bit pattern happens to exist present in the storage, which might not even represent a valid value for that type). If the program attempts to access an uninitialized value, the results are undefined. Many modernistic compilers endeavor to observe and warn nigh this trouble, but both faux positives and simulated negatives tin can occur.

Heap retentivity allocation has to exist synchronized with its actual usage in whatever program to be reused every bit much as possible. For case, if the only arrow to a heap retentiveness allotment goes out of telescopic or has its value overwritten before information technology is deallocated explicitly, and so that retentivity cannot be recovered for later on reuse and is essentially lost to the program, a phenomenon known equally a memory leak. Conversely, it is possible for memory to be freed, but is referenced subsequently, leading to unpredictable results. Typically, the failure symptoms appear in a portion of the program unrelated to the code that causes the error, making information technology difficult to diagnose the failure. Such issues are ameliorated in languages with automatic garbage drove.

Libraries [edit]

The C programming linguistic communication uses libraries as its primary method of extension. In C, a library is a ready of functions contained within a single "annal" file. Each library typically has a header file, which contains the prototypes of the functions independent inside the library that may exist used past a program, and declarations of special data types and macro symbols used with these functions. In lodge for a program to apply a library, information technology must include the library'due south header file, and the library must exist linked with the plan, which in many cases requires compiler flags (eastward.grand., -lm, shorthand for "link the math library").^[31]

The almost mutual C library is the C standard library, which is specified by the ISO and ANSI C standards and comes with every C implementation (implementations which target limited environments such every bit embedded systems may provide only a subset of the standard library). This library supports stream input and output, memory allocation, mathematics, character strings, and fourth dimension values. Several carve up standard headers (for case, stdio.h) specify the interfaces for these and other standard library facilities.

Another mutual gear up of C library functions are those used past applications specifically targeted for Unix and Unix-like systems, especially functions which provide an interface to the kernel. These functions are detailed in various standards such every bit POSIX and the Unmarried UNIX Specification.

Since many programs have been written in C, in that location are a wide multifariousness of other libraries available. Libraries are ofttimes written in C considering C compilers generate efficient object code; programmers then create interfaces to the library and then that the routines tin can be used from college-level languages like Coffee, Perl, and Python.^[31]

File treatment and streams [edit]

File input and output (I/O) is not part of the C language itself but instead is handled past libraries (such every bit the C standard library) and their associated header files (eastward.g. stdio.h). File handling is generally implemented through high-level I/O which works through streams. A stream is from this perspective a information flow that is independent of devices, while a file is a concrete device. The high-level I/O is done through the association of a stream to a file. In the C standard library, a buffer (a retentivity surface area or queue) is temporarily used to shop information before information technology's sent to the final destination. This reduces the time spent waiting for slower devices, for case a hard bulldoze or solid state bulldoze. Depression-level I/O functions are not part of the standard C library^{[ clarification needed ]} just are more often than not part of "bare metal" programming (programming that's independent of whatever operating system such as most embedded programming). With few exceptions, implementations include low-level I/O.

Linguistic communication tools [edit]

A number of tools have been adult to assistance C programmers observe and prepare statements with undefined behavior or possibly erroneous expressions, with greater rigor than that provided by the compiler. The tool lint was the first such, leading to many others.

Automated source code checking and auditing are beneficial in any language, and for C many such tools exist, such every bit Lint. A common practice is to utilize Lint to detect questionable code when a program is kickoff written. Once a program passes Lint, it is so compiled using the C compiler. Also, many compilers can optionally warn about syntactically valid constructs that are probable to really exist errors. MISRA C is a proprietary set of guidelines to avoid such questionable code, developed for embedded systems.^[37]

There are likewise compilers, libraries, and operating system level mechanisms for performing actions that are non a standard part of C, such as premises checking for arrays, detection of buffer overflow, serialization, dynamic memory tracking, and automatic garbage collection.

Tools such as Purify or Valgrind and linking with libraries containing special versions of the memory allocation functions tin help uncover runtime errors in retentivity usage.

Uses [edit]

The C Programming Language

C is widely used for systems programming in implementing operating systems and embedded system applications,^[38] because C code, when written for portability, tin be used for most purposes, withal when needed, system-specific lawmaking tin be used to admission specific hardware addresses and to perform blazon punning to friction match externally imposed interface requirements, with a low run-fourth dimension need on system resource.

C can be used for website programming using the Mutual Gateway Interface (CGI) as a "gateway" for information betwixt the Web application, the server, and the browser.^[39] C is often chosen over interpreted languages because of its speed, stability, and near-universal availability.^[forty]

A effect of C'southward broad availability and efficiency is that compilers, libraries and interpreters of other programming languages are often implemented in C. For case, the reference implementations of Python, Perl, Ruby, and PHP are written in C.

C enables programmers to create efficient implementations of algorithms and information structures, because the layer of brainchild from hardware is thin, and its overhead is low, an of import benchmark for computationally intensive programs. For case, the GNU Multiple Precision Arithmetic Library, the GNU Scientific Library, Mathematica, and MATLAB are completely or partially written in C.

C is sometimes used equally an intermediate language by implementations of other languages. This approach may exist used for portability or convenience; by using C as an intermediate language, additional machine-specific code generators are non necessary. C has some features, such every bit line-number preprocessor directives and optional superfluous commas at the end of initializer lists, that support compilation of generated code. However, some of C's shortcomings have prompted the development of other C-based languages specifically designed for utilise equally intermediate languages, such as C--.

C has besides been widely used to implement end-user applications. However, such applications tin likewise be written in newer, higher-level languages.

[edit]

The TIOBE index graph, showing a comparison of the popularity of diverse programming languages^[41]

C has both straight and indirectly influenced many later languages such every bit C#, D, Become, Java, JavaScript, Limbo, LPC, Perl, PHP, Python, and Unix'due south C shell.^[42] The well-nigh pervasive influence has been syntactical; all of the languages mentioned combine the argument and (more than or less recognizably) expression syntax of C with type systems, data models, and/or large-calibration programme structures that differ from those of C, sometimes radically.

Several C or near-C interpreters exist, including Ch and CINT, which can too be used for scripting.

When object-oriented programming languages became pop, C++ and Objective-C were two different extensions of C that provided object-oriented capabilities. Both languages were originally implemented as source-to-source compilers; source code was translated into C, and and then compiled with a C compiler.^[43]

The C++ programming language (originally named "C with Classes") was devised by Bjarne Stroustrup as an approach to providing object-oriented functionality with a C-similar syntax.^[44] C++ adds greater typing strength, scoping, and other tools useful in object-oriented programming, and permits generic programming via templates. Nearly a superset of C, C++ now supports most of C, with a few exceptions.

Objective-C was originally a very "sparse" layer on top of C, and remains a strict superset of C that permits object-oriented programming using a hybrid dynamic/static typing paradigm. Objective-C derives its syntax from both C and Smalltalk: syntax that involves preprocessing, expressions, office declarations, and part calls is inherited from C, while the syntax for object-oriented features was originally taken from Smalltalk.

In addition to C++ and Objective-C, Ch, Cilk, and Unified Parallel C are nearly supersets of C.

Notes [edit]

^ The original case code volition compile on most mod compilers that are not in strict standard compliance manner, but information technology does not fully conform to the requirements of either C89 or C99. In fact, C99 requires that a diagnostic message be produced.
^ The main office actually has ii arguments, int argc and char *argv[], respectively, which can exist used to handle command line arguments. The ISO C standard (section 5.1.2.ii.1) requires both forms of primary to be supported, which is special treatment non afforded to any other function.

References [edit]

^ ^a ^b Kernighan, Brian Westward.; Ritchie, Dennis M. (February 1978). The C Programming Linguistic communication (1st ed.). Englewood Cliffs, NJ: Prentice Hall. ISBN978-0-13-110163-0.
^ Ritchie (1993): "Thompson had made a cursory attempt to produce a organisation coded in an early on version of C—earlier structures—in 1972, but gave up the effort."
^ Fruderica (December 13, 2020). "History of C". The cppreference.com. Archived from the original on October 24, 2020. Retrieved October 24, 2020.
^ Ritchie (1993): "The scheme of type limerick adopted by C owes considerable debt to Algol 68, although it did not, perhaps, emerge in a form that Algol's adherents would approve of."
^ Ring Team (Oct 23, 2021). "The Band programming language and other languages". ring-lang.net.
^ ^a ^b "Verilog HDL (and C)" (PDF). The Research School of Figurer Science at the Australian National University. June 3, 2010. Archived from the original (PDF) on Nov 6, 2013. Retrieved August nineteen, 2013. 1980s: ; Verilog first introduced ; Verilog inspired by the C programming language
^ ^a ^b ^c ^d ^e Ritchie (1993)
^ "Programming Language Popularity". 2009. Archived from the original on January 16, 2009. Retrieved January 16, 2009.
^ "TIOBE Programming Community Index". 2009. Archived from the original on May 4, 2009. Retrieved May six, 2009.
^ ^a ^b "History of C". en.cppreference.com. Archived from the original on May 29, 2018. Retrieved May 28, 2018.
^ "TIOBE Alphabetize for October 2021". Retrieved October 7, 2021.
^ Ritchie, Dennis. "BCPL to B to C". Archived from the original on December 12, 2019. Retrieved September 10, 2019.
^ ^a ^b Johnson, S. C.; Ritchie, D. M. (1978). "Portability of C Programs and the UNIX System". Bong System Tech. J. 57 (6): 2021–2048. CiteSeerXten.1.ane.138.35. doi:ten.1002/j.1538-7305.1978.tb02141.x. S2CID 17510065. (Note: The PDF is an OCR scan of the original, and contains a rendering of "IBM 370" as "IBM 310".)
^ McIlroy, M. D. (1987). A Research Unix reader: annotated excerpts from the Developer's Manual, 1971–1986 (PDF) (Technical report). CSTR. Bong Labs. p. 10. 139. Archived (PDF) from the original on November 11, 2017. Retrieved Feb ane, 2015.
^ "C transmission pages". FreeBSD Miscellaneous Information Manual (FreeBSD xiii.0 ed.). May 30, 2011. Archived from the original on Jan 21, 2021. Retrieved Jan 15, 2021. [ane] Archived January 21, 2021, at the Wayback Auto
^ Kernighan, Brian W.; Ritchie, Dennis 1000. (March 1988). The C Programming Language (2nd ed.). Englewood Cliffs, NJ: Prentice Hall. ISBN978-0-13-110362-vii.
^ Stroustrup, Bjarne (2002). Sibling rivalry: C and C++ (PDF) (Report). AT&T Labs. Archived (PDF) from the original on August 24, 2014. Retrieved April xiv, 2014.
^ C Integrity. International Organisation for Standardization. March 30, 1995. Archived from the original on July 25, 2018. Retrieved July 24, 2018.
^ "JTC1/SC22/WG14 – C". Home page. ISO/IEC. Archived from the original on Feb 12, 2018. Retrieved June ii, 2011.
^ Andrew Binstock (October 12, 2011). "Interview with Herb Sutter". Dr. Dobbs. Archived from the original on August ii, 2013. Retrieved September 7, 2013.
^ "Revised C23 Schedule WG fourteen N 2759" (PDF). world wide web.open-std.org. Archived (PDF) from the original on June 24, 2021. Retrieved October x, 2021.
^ "TR 18037: Embedded C" (PDF). ISO / IEC. Archived (PDF) from the original on February 25, 2021. Retrieved July 26, 2011.
^ Harbison, Samuel P.; Steele, Guy L. (2002). C: A Reference Transmission (5th ed.). Englewood Cliffs, NJ: Prentice Hall. ISBN978-0-13-089592-9. Contains a BNF grammar for C.
^ Kernighan & Ritchie (1996), p. 192.
^ Kernighan & Ritchie (1978), p. iii.
^ "ISO/IEC 9899:201x (ISO C11) Committee Typhoon" (PDF). Archived (PDF) from the original on December 22, 2017. Retrieved September 16, 2011.
^ Kernighan & Ritchie (1996), pp. 192, 259.
^ "10 Mutual Programming Mistakes in C++". Cs.ucr.edu. Archived from the original on October 21, 2008. Retrieved June 26, 2009.
^ Schultz, Thomas (2004). C and the 8051 (3rd ed.). Otsego, MI: PageFree Publishing Inc. p. twenty. ISBN978-1-58961-237-2. Archived from the original on July 29, 2020. Retrieved Feb 10, 2012.
^ Kernighan & Ritchie (1978), p. half-dozen.
^ ^a ^b ^c ^d ^e ^f ^g Klemens, Ben (2013). 21st Century C. O'Reilly Media. ISBN978-1-4493-2714-9.
^ Feuer, Alan R.; Gehani, Narain H. (March 1982). "Comparison of the Programming Languages C and Pascal". ACM Computing Surveys. 14 (i): 73–92. doi:ten.1145/356869.356872. S2CID 3136859.
^ Kernighan & Ritchie (1996), p. 122.
^ For example, gcc provides _FORTIFY_SOURCE. "Security Features: Compile Time Buffer Checks (FORTIFY_SOURCE)". fedoraproject.org. Archived from the original on January 7, 2007. Retrieved August 5, 2012.
^ เอี่ยมสิริวงศ์, โอภาศ (2016). Programming with C. Bangkok, Thailand: SE-Education PUBLIC COMPANY LIMITED. pp. 225–230. ISBN978-616-08-2740-4.
^ Raymond, Eric South. (Oct 11, 1996). The New Hacker's Dictionary (third ed.). MIT Printing. p. 432. ISBN978-0-262-68092-9. Archived from the original on Nov 12, 2012. Retrieved August five, 2012.
^ "Man Page for lint (freebsd Department 1)". unix.com. May 24, 2001. Retrieved July 15, 2014.
^ Dale, Nell B.; Weems, Chip (2014). Programming and trouble solving with C++ (sixth ed.). Burlington, MA: Jones & Bartlett Learning. ISBN978-1449694289. OCLC 894992484.
^ Dr. Dobb's Sourcebook. U.S.A.: Miller Freeman, Inc. Nov–December 1995.
^ "Using C for CGI Programming". linuxjournal.com. March ane, 2005. Archived from the original on February xiii, 2010. Retrieved January four, 2010.
^ McMillan, Robert (August 1, 2013). "Is Java Losing Its Mojo?". Wired. Archived from the original on Feb fifteen, 2017. Retrieved March 5, 2017.
^ O'Regan, Gerard (September 24, 2015). Pillars of computing : a compendium of select, pivotal technology firms. ISBN978-3319214641. OCLC 922324121.
^ Rauchwerger, Lawrence (2004). Languages and compilers for parallel calculating : 16th international workshop, LCPC 2003, College Station, TX, USA, October two-4, 2003 : revised papers. Springer. ISBN978-3540246442. OCLC 57965544.
^ Stroustrup, Bjarne (1993). "A History of C++: 1979−1991" (PDF). Archived (PDF) from the original on February ii, 2019. Retrieved June 9, 2011.

Sources [edit]

Ritchie, Dennis M. (March 1993). "The Development of the C Linguistic communication". ACM SIGPLAN Notices. ACM. 28 (3): 201–208. doi:10.1145/155360.155580.
Ritchie, Dennis M. (1993). "The Development of the C Linguistic communication". The Second ACM SIGPLAN Conference on History of Programming Languages (HOPL-2). ACM. pp. 201–208. doi:10.1145/154766.155580. ISBN0-89791-570-iv . Retrieved November 4, 2014.
Kernighan, Brian West.; Ritchie, Dennis M. (1996). The C Programming Language (2nd ed.). Prentice Hall. ISBN7-302-02412-X.

External links [edit]

ISO C Working Group official website
- ISO/IEC 9899, publicly available official C documents, including the C99 Rationale
- "C99 with Technical corrigenda TC1, TC2, and TC3 included" (PDF). (3.61 MB)
comp.lang.c Frequently Asked Questions
A History of C, by Dennis Ritchie

timmermantherer.blogspot.com

Source: https://en.wikipedia.org/wiki/C_(programming_language)