C# Read a String From Xml File

General-purpose programming linguistic communication

C
Major implementations
The C Programming Language ^[1] (ofttimes referred to as M&R), the seminal book on C
Paradigm	Multi-paradigm: imperative (procedural), structured
Designed by	Dennis Ritchie
Developer	Dennis Ritchie & Bell Labs (creators); ANSI X3J11 (ANSI C); ISO/IEC JTC1/SC22/WG14 (ISO C)
Starting time appeared	1972; l years ago (1972) ^[2]

Stable release	C17 / June 2018; 3 years ago (2018-06)
Preview release	C2x (N2731) / October xviii, 2021; four months ago (2021-10-18) ^[3]

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

C (, as in the letter c) is a full general-purpose, procedural computer programming language supporting structured programming, lexical variable scope, and recursion, with a static type organization. By design, C provides constructs that map efficiently to typical machine instructions. Information technology has plant lasting use in applications previously coded in associates linguistic communication. Such applications include operating systems and diverse application software for calculator architectures that range from supercomputers to PLCs and embedded systems.

A successor to the programming linguistic communication 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 become one of the near widely used programming languages,^[8] ^[9] with C compilers from various vendors available for the majority of existing reckoner architectures and operating systems. C has been standardized by ANSI since 1989 (ANSI C) and by the International System for Standardization (ISO).

C is an imperative procedural language. It was designed to be compiled to provide low-level access to memory and language constructs that map efficiently to machine instructions, all with minimal runtime support. Despite its low-level capabilities, the linguistic communication was designed to encourage cross-platform programming. A standards-compliant C programme written with portability in heed tin exist compiled for a wide variety of computer platforms and operating systems with few changes to its source code.^[10]

Since 2000, C has consistently ranked amid the top two languages in the TIOBE index, a measure of the popularity of programming languages.^[11]

Overview [edit]

Like most procedural languages in the ALGOL tradition, C has facilities for structured programming and allows lexical variable scope and recursion. Its static type system prevents unintended operations. In C, all executable code is contained inside subroutines (also called "functions", though non strictly in the sense of functional programming). Part parameters are ever passed by value (except arrays). Laissez passer-by-reference is imitation in C by explicitly passing arrow values. C program source text is free-format, using the semicolon equally a statement terminator and curly braces for grouping blocks of statements.

The C linguistic communication also exhibits the following characteristics:

The language has a small, stock-still number of keywords, including a full set of control menstruum primitives: if/else, for, practise/while, while, and switch. User-divers names are not distinguished from keywords by any kind of sigil.
Information technology has a big number of arithmetic, bitwise, and logic operators: +,+=,++,&,||, etc.
More than one assignment may exist performed in a single argument.
Functions:
- Part return values can be ignored, when not needed.
- Part and data pointers permit advertisement hoc run-time polymorphism.
- Functions may not exist defined inside the lexical telescopic of other functions.
Data typing is static, just weakly enforced; all data has a type, simply implicit conversions are possible.
Declaration syntax mimics usage context. C has no "define" keyword; instead, a statement beginning with the name of a type is taken every bit a proclamation. There is no "function" keyword; instead, a function is indicated by the presence of a parenthesized argument list.
User-defined (typedef) and chemical compound types are possible.
- Heterogeneous aggregate data types (struct) allow related data elements to be accessed and assigned every bit a unit.
- Union is a structure with overlapping members; merely the terminal member stored is valid.
- Array indexing is a secondary annotation, defined in terms of pointer arithmetic. Unlike structs, arrays are non first-grade objects: they cannot be assigned or compared using single born operators. There is no "array" keyword in utilise or definition; instead, foursquare brackets betoken arrays syntactically, for example month[11].
- Enumerated types are possible with the enum keyword. They are freely interconvertible with integers.
- Strings are not a singled-out data type, but are conventionally implemented as null-terminated grapheme arrays.
Low-level access to figurer memory is possible by converting car addresses to typed pointers.
Procedures (subroutines not returning values) are a special case of function, with an untyped return type void.
A preprocessor performs macro definition, source code file inclusion, and provisional compilation.
At that place is a basic form of modularity: files can be compiled separately and linked together, with command over which functions and information objects are visible to other files via static and extern attributes.
Complex functionality such as I/O, string manipulation, and mathematical functions are consistently delegated to library routines.

While C does not include certain features found in other languages (such as object orientation and garbage collection), these tin can be implemented or emulated, often through the use of external libraries (e.grand., the GLib Object System or the Boehm garbage collector).

Relations to other languages [edit]

Many later languages have borrowed straight or indirectly from C, including C++, C#, Unix's C beat out, D, Get, Java, JavaScript (including transpilers), Julia, Limbo, LPC, Objective-C, Perl, PHP, Python, Ruby, Rust, Swift, Verilog and SystemVerilog (hardware description languages).^[six] These languages have drawn many of their command structures and other bones features from C. Near of them (Python being a dramatic exception) also express highly similar syntax to C, and they tend to combine the recognizable expression and argument syntax of C with underlying blazon systems, data models, and semantics that can be radically different.

History [edit]

Early developments [edit]

Timeline of language development
Year	C Standard^[ten]
1972	Birth
1978	Thou&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 assembly language on a PDP-seven 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-11 version of Unix was as well developed in associates language.^[seven]

Thompson desired a programming linguistic communication to make utilities for the new platform. At outset, he tried to make a Fortran compiler, but soon gave upwardly the idea. Instead, he created a cut-downwards version of the recently developed BCPL systems programming linguistic communication. The official description of BCPL was not available at the time,^[12] and Thompson modified the syntax to exist less wordy, producing the similar but somewhat simpler B.^[seven] Yet, few utilities were ultimately written in B because it was besides boring, and B could non have advantage of PDP-11 features such equally byte addressability.

In 1972, Ritchie started to improve B, most notably adding data typing for variables, which resulted in creating a new language C.^[xiii] The C compiler and some utilities fabricated with it were included in Version ii Unix.^[14]

At Version four Unix, released in November 1973, the Unix kernel was extensively re-implemented in C.^[7] Past this time, the C linguistic communication had acquired some powerful features such as struct types.

The preprocessor was introduced around 1973 at the urging of Alan Snyder and also in recognition of the usefulness of the file-inclusion mechanisms bachelor in BCPL and PL/I. Its original version provided merely included files and simple string replacements: #include and #ascertain of parameterless macros. Presently after that, it was extended, mostly by Mike Lesk and and so past John Reiser, to incorporate macros with arguments and conditional compilation.^[seven]

Unix was one of the start operating system kernels implemented in a language other than assembly. Earlier instances include the Multics system (which was written in PL/I) and Master Command 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 organisation. Johnson'due south Portable C Compiler served every bit the basis for several implementations of C on new platforms.^[13]

K&R C [edit]

In 1978, Brian Kernighan and Dennis Ritchie published the showtime edition of The C Programming Language.^[1] This book, known to C programmers as K&R, served for many years as an breezy specification of the language. The version of C that it describes is usually referred to equally "K&R C". As this was released in 1978, it is too referred to as C78.^[15] The 2nd edition of the book^[16] covers the afterwards ANSI C standard, described below.

K&R introduced several linguistic communication features:

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

Fifty-fifty later on the publication of the 1989 ANSI standard, for many years One thousand&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 however in utilise, and considering carefully written K&R C code can be legal Standard C as well.

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

For example:

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

The int blazon specifiers which are commented out could be omitted in K&R C, but are required in later standards.

Since Yard&R function declarations did not include whatsoever information about function arguments, function parameter type checks were not performed, although some compilers would result a warning message if a local function was called with the wrong number of arguments, or if multiple calls to an external role used different numbers or types of arguments. Split tools such every bit Unix'south lint utility were developed that (amongst other things) could check for consistency of role employ across multiple source files.

In the years post-obit the publication of Thousand&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 union types (rather than pointers)
assignment for struct data types
enumerated types

The large number of extensions and lack of understanding on a standard library, together with the language popularity and the fact that not even the Unix compilers precisely implemented the Thousand&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 diversity 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 get the ground for the 1988 POSIX standard. In 1989, the C standard was ratified as ANSI X3.159-1989 "Programming Linguistic communication C". This version of the linguistic communication is oftentimes referred to every bit ANSI C, Standard C, or sometimes C89.

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

ANSI, like other national standards bodies, no longer develops the C standard independently, but 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.

I of the aims of the C standardization process was to produce a superset of K&R C, incorporating many of the subsequently introduced unofficial features. The standards committee besides included several additional features such equally office 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 fashion used in C++, the G&R interface continued to be permitted, for compatibility with existing source code.

C89 is supported by current C compilers, and most modernistic C code is based on it. Whatsoever program written just in Standard C and without whatever hardware-dependent assumptions will run correctly on any platform with a conforming C implementation, within its resource limits. Without such precautions, programs may compile but on a sure platform or with a particular compiler, due, for example, to the use of not-standard libraries, such as GUI libraries, or to a reliance on compiler- or platform-specific attributes such every bit the exact size of data types and byte endianness.

In cases where code must be compilable past either standard-conforming or K&R C-based compilers, the __STDC__ macro can be used to split up the code into Standard and K&R sections to forestall the use on a K&R C-based compiler of features bachelor merely in Standard C.

After the ANSI/ISO standardization procedure, 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 equally C95) was published, to correct some details and to add more extensive support for international character sets.^[18]

C99 [edit]

The C standard was farther revised in the tardily 1990s, leading to the publication of ISO/IEC 9899:1999 in 1999, which is usually referred to as "C99". Information technology has since been amended 3 times by Technical Corrigenda.^[19]

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

C99 is for the nearly office backward compatible with C90, but is stricter in some ways; in detail, a annunciation that lacks a type specifier no longer has int implicitly causeless. A standard macro __STDC_VERSION__ is defined with value 199901L to indicate that C99 back up is available. 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++, withal, 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 / role names) in the form of escaped characters (e.g. \U0001f431) is now required. Support 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 commission adopted guidelines to limit the adoption of new features that had not been tested by existing implementations.

The C11 standard adds numerous new features to C and the library, including type generic macros, anonymous structures, improved Unicode support, diminutive 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 point that C11 back up is bachelor.

C17 [edit]

Published in June 2018, C17 is the current standard for the C programming linguistic communication. It introduces no new language features, only technical corrections, and clarifications to defects in C11. The standard macro __STDC_VERSION__ is defined as 201710L.

C2x [edit]

C2x is an informal name for the next (afterward 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 linguistic communication in gild to support exotic features such every bit fixed-point arithmetics, multiple singled-out memory banks, and basic I/O operations.

In 2008, the C Standards Commission published a technical report extending the C linguistic communication^[22] to address these issues by providing a mutual standard for all implementations to adhere to. It includes a number of features non available in normal C, such as stock-still-bespeak arithmetics, named address spaces, and basic I/O hardware addressing.

Syntax [edit]

C has a formal grammer specified by the C standard.^[23] Line endings are by and large not significant in C; even so, line boundaries do accept significance during the preprocessing stage. Comments may appear either between the delimiters /* and */, or (since C99) post-obit // until the cease of the line. Comments delimited by /* and */ do not nest, and these sequences of characters are not interpreted as comment delimiters if they appear within string or graphic symbol 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 equally struct, union, and enum, or assign types to and perhaps reserve storage for new variables, usually by writing the type followed by the variable proper noun. Keywords such equally char and int specify built-in types. Sections of lawmaking are enclosed in braces ({ and }, sometimes called "curly brackets") to limit the scope of declarations and to act every bit a single statement for control structures.

As an imperative language, C uses statements to specify actions. The most common statement is an expression statement, consisting of an expression to be evaluated, followed past a semicolon; as a side effect 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-menses statements identified past reserved keywords. Structured programming is supported by if … [else] provisional execution and past do … while, while, and for iterative execution (looping). The for statement has dissever initialization, testing, and reinitialization expressions, any or all of which can be omitted. break and go on tin exist used to leave the innermost enclosing loop argument or skip to its reinitialization. There is also a non-structured goto statement which branches straight to the designated characterization inside the part. switch selects a case to be executed based on the value of an integer expression.

Expressions can utilize a variety of born operators and may contain role calls. The order in which arguments to functions and operands to most operators are evaluated is unspecified. The evaluations may even exist interleaved. Nevertheless, all side effects (including storage to variables) will occur earlier the next "sequence betoken"; sequence points include the end of each expression statement, and the entry to and render from each role 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 take more intendance to obtain reliable results than is needed for other programming languages.

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

Character ready [edit]

The bones C source character ready includes the post-obit characters:

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

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

Additional multi-byte encoded characters may exist 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 character), although this characteristic is not yet widely implemented.

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

Reserved words [edit]

C89 has 32 reserved words, as well known as keywords, which are the words that cannot be used for whatever purposes other than those for which they are predefined:

machine
break
example
char
const
proceed
default
exercise
double
else
enum
extern
float
for
goto
if
int
long
register
return
short
signed
sizeof
static
struct
switch
typedef
marriage
unsigned
void
volatile
while

C99 reserved five more words:

_Bool
_Complex
_Imaginary
inline
restrict

C11 reserved seven more words:^[26]

_Alignas
_Alignof
_Atomic
_Generic
_Noreturn
_Static_assert
_Thread_local

Most of the recently reserved words begin with an underscore followed by a majuscule letter, because identifiers of that form were previously reserved by the C standard for use but past implementations. Since existing program source code should not have been using these identifiers, it would not exist affected when C implementations started supporting these extensions to the programming linguistic communication. Some standard headers do define more convenient synonyms for underscored identifiers. The language previously included a reserved word called entry, but this was seldom implemented, and has now been removed equally a reserved word.^[27]

Operators [edit]

C supports a rich prepare 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: +, -, *, /, %
assignment: =
augmented assignment: +=, -=, *=, /=, %=, &=, |=, ^=, <<=, >>=
bitwise logic: ~, &, |, ^
bitwise shifts: <<, >>
boolean logic: !, &&, ||
conditional evaluation: ? :
equality testing: ==, !=
calling functions: ( )
increment and decrement: ++, --
member option: ., ->
object size: sizeof
order relations: <, <=, >, >=
reference and dereference: &, *, [ ]
sequencing: ,
subexpression grouping: ( )
type conversion: (typename)

C uses the operator = (used in mathematics to limited equality) to indicate assignment, following the precedent of Fortran and PL/I, just unlike ALGOL and its derivatives. C uses the operator == to test for equality. The similarity between these ii operators (assignment and equality) may event in the adventitious use of one in identify of the other, and in many cases, the mistake does not produce an mistake message (although some compilers produce warnings). For example, the provisional expression if (a == b + 1) might mistakenly be written as if (a = b + ane), which will be evaluated as true if a is not zero after the assignment.^[28]

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

"Hello, world" case [edit]

The "how-do-you-do, world" example, which appeared in the kickoff edition of Grand&R, has become the model for an introductory program in most programming textbooks. The program prints "hello, world" to the standard output, which is usually a last or screen display.

The original version was:^[thirty]

                        main            ()                        {                                                printf            (            "hello, world            \due north            "            );                        }

A standard-befitting "hello, earth" program is:^[a]

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

The commencement line of the program contains a preprocessing directive, indicated by #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 as 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 aforementioned proper noun, as opposed to double quotes which typically include local or project-specific header files.

The next line indicates that a function named main is beingness defined. The main role serves a special purpose in C programs; the run-time surround calls the main office 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) as a result of evaluating the main function, is an integer. The keyword void as a parameter list indicates that this function takes no arguments.^[b]

The opening curly caryatid indicates the commencement of the definition of the primary function.

The next line calls (diverts execution to) a function named printf, which in this case is supplied from a organization library. In this call, the printf role is passed (provided with) a unmarried argument, the address of the first character in the string literal "hello, world\northward". The string literal is an unnamed assortment with elements of type char, set automatically by the compiler with a final 0-valued grapheme to mark the end of the assortment (printf needs to know this). The \n is an escape sequence that C translates to a newline character, which on output signifies the end of the current line. The return value of the printf function is of type int, but it is silently discarded since information technology is not used. (A more conscientious program might test the return value to determine whether or not the printf function succeeded.) The semicolon ; terminates the statement.

The closing curly caryatid indicates the cease of the code for the primary function. According to the C99 specification and newer, the chief function, unlike any other role, will implicitly return a value of 0 upon reaching the } that terminates the function. (Formerly an explicit return 0; statement was required.) This is interpreted by the run-time arrangement as an go out code 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 equally Pascal.^[32] There are built-in types for integers of various sizes, both signed and unsigned, floating-indicate numbers, and enumerated types (enum). Integer blazon char is oft used for single-byte characters. C99 added a boolean datatype. There are besides derived types including arrays, pointers, records (struct), and unions (spousal relationship).

C is ofttimes used in low-level systems programming where escapes from the type system may be necessary. The compiler attempts to ensure type correctness of near expressions, simply the programmer tin override the checks in various ways, either past using a blazon bandage to explicitly convert a value from one type to another, or past using pointers or unions to reinterpret the underlying bits of a data object in some other mode.

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

C'southward usual arithmetic conversions allow for efficient lawmaking to be generated, but can sometimes produce unexpected results. For example, a comparison 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 use of pointers, a type of reference that records the accost or location of an object or part in retentiveness. Pointers can exist dereferenced to access data stored at the accost pointed to, or to invoke a pointed-to office. Pointers tin be manipulated using assignment or pointer arithmetic. The run-time representation of a arrow value is typically a raw retentivity address (mayhap augmented past an offset-inside-word field), but since a arrow's type includes the blazon of the thing pointed to, expressions including pointers can exist type-checked at compile time. Pointer arithmetics is automatically scaled by the size of the pointed-to data type. Pointers are used for many purposes in C. Text strings are commonly manipulated using pointers into arrays of characters. Dynamic memory allocation is performed using pointers. Many data types, such as 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 past event handlers.^[31]

A nil arrow value explicitly points to no valid location. Dereferencing a null pointer value is undefined, often resulting in a partition error. Null pointer values are useful for indicating special cases such as no "next" arrow in the final node of a linked listing, or as an error indication from functions returning pointers. In appropriate contexts in source code, such equally for assigning to a arrow variable, a null pointer constant tin be written as 0, with or without explicit casting to a pointer type, or as the NULL macro defined by several standard headers. In conditional contexts, null pointer values evaluate to false, while all other arrow values evaluate to truthful.

Void pointers (void *) point to objects of unspecified type, and can therefore exist used as "generic" data 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 immune, although they can easily be (and in many contexts implicitly are) converted to and from any other object arrow type.^[31]

Careless employ of pointers is potentially dangerous. Because they are typically unchecked, a pointer variable can be made to betoken to any capricious location, which can crusade undesirable furnishings. Although properly used pointers point to safe places, they tin can be made to betoken to unsafe places past using invalid pointer arithmetic; the objects they point to may go on to be used afterwards deallocation (dangling pointers); they may be used without having been initialized (wild pointers); or they may be directly assigned an unsafe value using a cast, matrimony, or through another corrupt pointer. In general, C is permissive in allowing manipulation of and conversion between arrow types, although compilers typically provide options for various levels of checking. Some other programming languages address these bug past using more restrictive reference types.

Arrays [edit]

Array types in C are traditionally of a fixed, static size specified at compile time. The more than recent C99 standard as well allows a form of variable-length arrays. Notwithstanding, it is also possible to classify a block of memory (of arbitrary size) at run-time, using the standard library's malloc function, and treat it as an array.

Since arrays are always accessed (in effect) via pointers, array accesses are typically non checked confronting the underlying assortment size, although some compilers may provide bounds checking as an option.^[34] ^[35] Array bounds violations are therefore possible and tin lead to diverse repercussions, including illegal memory accesses, corruption of data, buffer overruns, and run-time exceptions.

C does not accept a special provision for declaring multi-dimensional arrays, but rather relies on recursion within the type system to declare arrays of arrays, which effectively accomplishes the same affair. The index values of the resulting "multi-dimensional array" can exist idea of every bit increasing in row-major order. Multi-dimensional arrays are unremarkably used in numerical algorithms (mainly from applied linear algebra) to store matrices. The structure of the C array is well suited to this particular task. Yet, in early versions of C the premises of the array must be known stock-still values or else explicitly passed to any subroutine that requires them, and dynamically sized arrays of arrays cannot exist accessed using double indexing. (A workaround for this was to allocate the array with an additional "row vector" of pointers to the columns.) C99 introduced "variable-length arrays" which address this issue.

The following example using modern C (C99 or subsequently) shows allocation of a two-dimensional assortment on the heap and the use of multi-dimensional array indexing for accesses (which tin can employ premises-checking on many C compilers):

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

Array–pointer interchangeability [edit]

The subscript note x[i] (where 10 designates a pointer) is syntactic sugar for *(x+i).^[36] Taking advantage of the compiler's noesis of the pointer type, the accost that x + i points to is non the base of operations address (pointed to by x) incremented by i bytes, but rather is defined to exist the base address incremented by i multiplied past the size of an element that x points to. Thus, 10[i] designates the i+anethursday element of the array.

Furthermore, in most expression contexts (a notable exception is as operand of sizeof), an expression of assortment type is automatically converted to a pointer to the assortment's first element. This implies that an array is never copied as a whole when named as an statement to a role, simply rather only the address of its outset chemical element is passed. Therefore, although function calls in C employ pass-by-value semantics, arrays are in effect passed past reference.

The total size of an array x tin exist adamant by applying sizeof to an expression of array type. The size of an element can be determined by applying the operator sizeof to any dereferenced chemical element of an array A, equally in n = sizeof A[0]. This, the number of elements in a alleged array A can be determined as sizeof A / sizeof A[0]. Note, that if simply a pointer to the first element is available every bit information technology is often the case in C lawmaking because of the automated conversion described above, the information about the total type of the array and its length are lost.

Memory management [edit]

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

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

These 3 approaches are appropriate in dissimilar situations and have various trade-offs. For case, static memory resource allotment has little allotment overhead, automatic resource allotment may involve slightly more overhead, and dynamic retention allotment can potentially have a great deal of overhead for both allotment and deallocation. The persistent nature of static objects is useful for maintaining state information across role calls, automatic allocation is easy to use but stack space is typically much more limited and transient than either static retentivity or heap infinite, and dynamic retentivity allocation allows convenient allocation of objects whose size is known only at run-time. Most C programs make extensive use of all three.

Where possible, automated or static allocation is usually simplest because the storage is managed by the compiler, freeing the programmer of the potentially error-prone chore of manually allocating and releasing storage. However, many data structures can modify in size at runtime, and since static allocations (and automated allocations before C99) must accept a fixed size at compile-fourth dimension, at that place are many situations in which dynamic allocation is necessary.^[31] Prior to the C99 standard, variable-sized arrays were a common example of this. (See the commodity on malloc for an instance of dynamically allocated arrays.) Dissimilar automatic allocation, which can neglect at run fourth dimension with uncontrolled consequences, the dynamic allocation functions return an indication (in the form of a naught arrow value) when the required storage cannot be allocated. (Static resource allotment that is besides large is usually detected past the linker or loader, before the program can even brainstorm execution.)

Unless otherwise specified, static objects contain zero or null pointer values upon program 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 be present in the storage, which might not fifty-fifty represent a valid value for that blazon). If the programme attempts to admission an uninitialized value, the results are undefined. Many modernistic compilers attempt to detect and warn about this problem, merely both false positives and false negatives can occur.

Heap retentiveness resource allotment has to be synchronized with its actual usage in any plan to be reused equally much every bit possible. For case, if the merely pointer to a heap retentivity allocation goes out of scope or has its value overwritten before it is deallocated explicitly, then that retention cannot be recovered for later on reuse and is essentially lost to the program, a phenomenon known as a retention leak. Conversely, it is possible for retention to be freed, but is referenced subsequently, leading to unpredictable results. Typically, the failure symptoms appear in a portion of the programme unrelated to the code that causes the fault, making it difficult to diagnose the failure. Such problems are ameliorated in languages with automatic garbage drove.

Libraries [edit]

The C programming language uses libraries as its primary method of extension. In C, a library is a prepare of functions independent inside a single "archive" file. Each library typically has a header file, which contains the prototypes of the functions contained within the library that may be used by a program, and declarations of special data types and macro symbols used with these functions. In order for a program to use a library, it must include the library'southward header file, and the library must be linked with the program, which in many cases requires compiler flags (east.g., -lm, autograph for "link the math library").^[31]

The most 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 as embedded systems may provide only a subset of the standard library). This library supports stream input and output, memory allotment, mathematics, character strings, and time values. Several split up standard headers (for example, stdio.h) specify the interfaces for these and other standard library facilities.

Another common prepare of C library functions are those used by applications specifically targeted for Unix and Unix-similar systems, especially functions which provide an interface to the kernel. These functions are detailed in diverse standards such as POSIX and the Single UNIX Specification.

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

File handling and streams [edit]

File input and output (I/O) is not function of the C language itself simply instead is handled by libraries (such as the C standard library) and their associated header files (e.1000. stdio.h). File handling is generally implemented through high-level I/O which works through streams. A stream is from this perspective a data flow that is contained of devices, while a file is a concrete device. The loftier-level I/O is done through the association of a stream to a file. In the C standard library, a buffer (a memory area or queue) is temporarily used to store information before it's sent to the final destination. This reduces the time spent waiting for slower devices, for example a hard bulldoze or solid state drive. Low-level I/O functions are not part of the standard C library^{[ clarification needed ]} but are generally part of "bare metal" programming (programming that's contained of any operating organisation such as most embedded programming). With few exceptions, implementations include depression-level I/O.

Language tools [edit]

A number of tools take been adult to aid C programmers notice and set statements with undefined beliefs or peradventure erroneous expressions, with greater rigor than that provided by the compiler. The tool lint was the offset such, leading to many others.

Automated source lawmaking checking and auditing are beneficial in any linguistic communication, and for C many such tools exist, such every bit Lint. A common practice is to use Lint to observe questionable lawmaking when a plan is offset written. Once a programme passes Lint, it is then compiled using the C compiler. Also, many compilers tin can optionally warn nigh syntactically valid constructs that are probable to actually be errors. MISRA C is a proprietary set of guidelines to avoid such questionable lawmaking, developed for embedded systems.^[37]

There are too compilers, libraries, and operating organization level mechanisms for performing actions that are not a standard part of C, such as bounds checking for arrays, detection of buffer overflow, serialization, dynamic memory tracking, and automated garbage collection.

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

Uses [edit]

The C Programming Linguistic communication

C is widely used for systems programming in implementing operating systems and embedded system applications,^[38] because C code, when written for portability, can exist used for near purposes, yet when needed, organization-specific code tin can be used to access specific hardware addresses and to perform type punning to match externally imposed interface requirements, with a depression run-time demand on system resource.

C tin 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 result of C'due south wide availability and efficiency is that compilers, libraries and interpreters of other programming languages are often implemented in C. For example, the reference implementations of Python, Perl, Ruby, and PHP are written in C.

C enables programmers to create efficient implementations of algorithms and data structures, because the layer of abstraction from hardware is sparse, and its overhead is low, an important criterion for computationally intensive programs. For instance, 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 past implementations of other languages. This approach may exist used for portability or convenience; by using C as an intermediate language, additional automobile-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 back up compilation of generated code. All the same, some of C's shortcomings accept prompted the evolution of other C-based languages specifically designed for utilize as intermediate languages, such as C--.

C has also been widely used to implement end-user applications. However, such applications can too be written in newer, higher-level languages.

[edit]

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

C has both directly and indirectly influenced many subsequently languages such as C#, D, Go, Coffee, JavaScript, Limbo, LPC, Perl, PHP, Python, and Unix'southward C shell.^[42] The most pervasive influence has been syntactical; all of the languages mentioned combine the statement and (more or less recognizably) expression syntax of C with type systems, data models, and/or large-scale program structures that differ from those of C, sometimes radically.

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

When object-oriented programming languages became popular, 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 so compiled with a C compiler.^[43]

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

Objective-C was originally a very "thin" layer on top of C, and remains a strict superset of C that permits object-oriented programming using a hybrid dynamic/static typing prototype. Objective-C derives its syntax from both C and Smalltalk: syntax that involves preprocessing, expressions, role declarations, and role 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.

Encounter also [edit]

Compatibility of C and C++
Comparing of Pascal and C
Comparison of programming languages
International Obfuscated C Code Contest
List of C-based programming languages
List of C compilers

Notes [edit]

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

References [edit]

^ ^a ^b Kernighan, Brian W.; 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 system coded in an early version of C—before structures—in 1972, but gave upwards 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 blazon composition adopted past C owes considerable debt to Algol 68, although information technology did non, maybe, emerge in a form that Algol's adherents would corroborate of."
^ Ring Squad (Oct 23, 2021). "The Ring programming language and other languages". ring-lang.net.
^ ^a ^b "Verilog HDL (and C)" (PDF). The Inquiry School of Informatics at the Australian National Academy. June 3, 2010. Archived from the original (PDF) on November 6, 2013. Retrieved August 19, 2013. 1980s: ; Verilog showtime introduced ; Verilog inspired by the C programming language
^ ^a ^b ^c ^d ^e Ritchie (1993)
^ "Programming Language Popularity". 2009. Archived from the original on Jan 16, 2009. Retrieved January 16, 2009.
^ "TIOBE Programming Community Index". 2009. Archived from the original on May 4, 2009. Retrieved May 6, 2009.
^ ^a ^b "History of C". en.cppreference.com. Archived from the original on May 29, 2018. Retrieved May 28, 2018.
^ "TIOBE Index for October 2021". Retrieved October vii, 2021.
^ Ritchie, Dennis. "BCPL to B to C". Archived from the original on Dec 12, 2019. Retrieved September ten, 2019.
^ ^a ^b Johnson, S. C.; Ritchie, D. Grand. (1978). "Portability of C Programs and the UNIX System". Bell System Tech. J. 57 (6): 2021–2048. CiteSeerX10.1.1.138.35. doi:x.1002/j.1538-7305.1978.tb02141.ten. S2CID 17510065. (Note: The PDF is an OCR scan of the original, and contains a rendering of "IBM 370" every bit "IBM 310".)
^ McIlroy, M. D. (1987). A Inquiry Unix reader: annotated excerpts from the Developer'southward Manual, 1971–1986 (PDF) (Technical report). CSTR. Bong Labs. p. 10. 139. Archived (PDF) from the original on Nov eleven, 2017. Retrieved February 1, 2015.
^ "C manual pages". FreeBSD Miscellaneous Information Transmission (FreeBSD 13.0 ed.). May 30, 2011. Archived from the original on January 21, 2021. Retrieved Jan xv, 2021. [ane] Archived January 21, 2021, at the Wayback Machine
^ Kernighan, Brian W.; Ritchie, Dennis Chiliad. (March 1988). The C Programming Language (2nd ed.). Englewood Cliffs, NJ: Prentice Hall. ISBN978-0-13-110362-7.
^ Stroustrup, Bjarne (2002). Sibling rivalry: C and C++ (PDF) (Study). AT&T Labs. Archived (PDF) from the original on August 24, 2014. Retrieved Apr 14, 2014.
^ C Integrity. International Organization 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 February 12, 2018. Retrieved June 2, 2011.
^ Andrew Binstock (October 12, 2011). "Interview with Herb Sutter". Dr. Dobbs. Archived from the original on August 2, 2013. Retrieved September 7, 2013.
^ "Revised C23 Schedule WG fourteen N 2759" (PDF). world wide web.open up-std.org. Archived (PDF) from the original on June 24, 2021. Retrieved October ten, 2021.
^ "TR 18037: Embedded C" (PDF). ISO / IEC. Archived (PDF) from the original on Feb 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. 3.
^ "ISO/IEC 9899:201x (ISO C11) Committee Typhoon" (PDF). Archived (PDF) from the original on Dec 22, 2017. Retrieved September xvi, 2011.
^ Kernighan & Ritchie (1996), pp. 192, 259.
^ "10 Common 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. xx. ISBN978-one-58961-237-2. Archived from the original on July 29, 2020. Retrieved February 10, 2012.
^ Kernighan & Ritchie (1978), p. half dozen.
^ ^a ^b ^c ^d ^{due east} ^f ^chiliad 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 (1): 73–92. doi:10.1145/356869.356872. S2CID 3136859.
^ Kernighan & Ritchie (1996), p. 122.
^ For example, gcc provides _FORTIFY_SOURCE. "Security Features: Compile Fourth dimension 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-Pedagogy PUBLIC COMPANY Express. pp. 225–230. ISBN978-616-08-2740-iv.
^ Raymond, Eric S. (October eleven, 1996). The New Hacker's Lexicon (3rd ed.). MIT Press. p. 432. ISBN978-0-262-68092-9. Archived from the original on Nov 12, 2012. Retrieved August five, 2012.
^ "Man Folio for lint (freebsd Department one)". unix.com. May 24, 2001. Retrieved July 15, 2014.
^ Dale, Nell B.; Weems, Scrap (2014). Programming and problem solving with C++ (sixth ed.). Burlington, MA: Jones & Bartlett Learning. ISBN978-1449694289. OCLC 894992484.
^ Dr. Dobb'southward Sourcebook. United statesA.: Miller Freeman, Inc. November–December 1995.
^ "Using C for CGI Programming". linuxjournal.com. March 1, 2005. Archived from the original on February 13, 2010. Retrieved January 4, 2010.
^ McMillan, Robert (August i, 2013). "Is Java Losing Its Mojo?". Wired. Archived from the original on February 15, 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 computing : 16th international workshop, LCPC 2003, College Station, TX, USA, Oct 2-four, 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 2, 2019. Retrieved June ix, 2011.

Sources [edit]

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

External links [edit]

ISO C Working Grouping 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 Oftentimes Asked Questions
A History of C, by Dennis Ritchie

delargiehatestaked.blogspot.com

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