C# Read Block of Data to Struct

General-purpose programming language

C
Major implementations
The C Programming Language ^[i] (oft referred to every bit K&R), the seminal volume on C
Paradigm	Multi-prototype: imperative (procedural), structured
Designed past	Dennis Ritchie
Developer	Dennis Ritchie & Bell Labs (creators); ANSI X3J11 (ANSI C); ISO/IEC JTC1/SC22/WG14 (ISO C)
Get-go appeared	1972; 50 years ago (1972) ^[2]

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

Typing bailiwick	Static, weak, manifest, nominal
OS	Cross-platform
Filename extensions	.c, .h
Website	www.iso.org/standard/74528.html world wide web.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] associates, PL/I, FORTRAN
Influenced
Numerous: AMPL, AWK, csh, C++, C--, C#, Objective-C, D, Become, Coffee, JavaScript, JS++, Julia, Limbo, LPC, Perl, PHP, Pike, Processing, Python, Ring,^[5]Rust, Seed7, Vala, Verilog (HDL),^[half-dozen] Nim, Zig
C Programming at Wikibooks

C (, as in the alphabetic character c) is a general-purpose, procedural estimator programming language supporting structured programming, lexical variable scope, and recursion, with a static type system. By pattern, C provides constructs that map efficiently to typical auto instructions. It has constitute lasting use in applications previously coded in assembly language. Such applications include operating systems and diverse application software for computer 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 past Dennis Ritchie betwixt 1972 and 1973 to construct utilities running on Unix. Information technology was applied to re-implementing the kernel of the Unix operating system.^[7] During the 1980s, C gradually gained popularity. It has go ane of the most widely used programming languages,^[eight] ^[ix] 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 past the International Organization 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 language was designed to encourage cross-platform programming. A standards-compliant C program written with portability in heed can be 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 among the top two languages in the TIOBE index, 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 scope and recursion. Its static type organisation prevents unintended operations. In C, all executable lawmaking is contained within subroutines (likewise called "functions", though not strictly in the sense of functional programming). Function parameters are e'er passed by value (except arrays). Pass-past-reference is simulated in C by explicitly passing pointer values. C program source text is free-format, using the semicolon equally a argument terminator and curly braces for grouping blocks of statements.

The C linguistic communication also exhibits the following characteristics:

The language has a minor, fixed number of keywords, including a full set of command flow primitives: if/else, for, practise/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 one assignment may be performed in a single statement.
Functions:
- Part return values can be ignored, when not needed.
- Function and information pointers permit ad hoc run-fourth dimension polymorphism.
- Functions may not exist defined within the lexical scope of other functions.
Data typing is static, but weakly enforced; all information has a type, but implicit conversions are possible.
Announcement syntax mimics usage context. C has no "define" keyword; instead, a statement beginning with the name of a type is taken as a declaration. There is no "function" keyword; instead, a function is indicated by the presence of a parenthesized argument list.
User-divers (typedef) and compound types are possible.
- Heterogeneous aggregate data types (struct) permit related data elements to be accessed and assigned every bit a unit.
- Spousal relationship is a construction with overlapping members; but the last member stored is valid.
- Array indexing is a secondary notation, divers in terms of pointer arithmetics. Unlike structs, arrays are not start-course objects: they cannot be assigned or compared using single congenital-in operators. There is no "array" keyword in use or definition; instead, foursquare brackets betoken arrays syntactically, for example month[xi].
- 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 every bit nada-terminated character arrays.
Low-level access to computer memory is possible past converting motorcar addresses to typed pointers.
Procedures (subroutines not returning values) are a special case of office, with an untyped return type void.
A preprocessor performs macro definition, source code file inclusion, and conditional compilation.
There is a basic course of modularity: files tin can be compiled separately and linked together, with control over which functions and information objects are visible to other files via static and extern attributes.
Complex functionality such every bit I/O, string manipulation, and mathematical functions are consistently delegated to library routines.

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

Relations to other languages [edit]

Many later languages have borrowed direct or indirectly from C, including C++, C#, Unix's C vanquish, D, Go, Java, JavaScript (including transpilers), Julia, Limbo, LPC, Objective-C, Perl, PHP, Python, Reddish, Rust, Swift, Verilog and SystemVerilog (hardware description languages).^[6] These languages have drawn many of their control structures and other basic features from C. Almost of them (Python being a dramatic exception) also express highly like 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 different.

History [edit]

Early developments [edit]

Timeline of language evolution
Yr	C Standard^[x]
1972	Birth
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 evolution 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 organisation to a PDP-11. The original PDP-11 version of Unix was also adult in assembly language.^[7]

Thompson desired a programming language to make utilities for the new platform. At first, he tried to make a Fortran compiler, but soon gave up the idea. Instead, he created a cutting-down version of the recently developed BCPL systems programming language. The official clarification 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.^[seven] However, few utilities were ultimately written in B because information technology was too slow, and B could non take reward of PDP-eleven features such as byte addressability.

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

At Version iv 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 equally struct types.

The preprocessor was introduced effectually 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 but included files and simple string replacements: #include and #define of parameterless macros. Shortly after that, it was extended, mostly by Mike Lesk and then by John Reiser, to incorporate macros with arguments and conditional compilation.^[7]

Unix was i of the showtime operating arrangement kernels implemented in a language other than assembly. Before 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 effectually 1977, Ritchie and Stephen C. Johnson made further changes to the language to facilitate portability of the Unix operating system. Johnson'southward Portable C Compiler served as the basis for several implementations of C on new platforms.^[xiii]

One thousand&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 One thousand&R, served for many years equally an breezy specification of the language. The version of C that it describes is commonly referred to as "Chiliad&R C". As this was released in 1978, it is likewise referred to equally C78.^[xv] The second edition of the book^[sixteen] covers the afterwards ANSI C standard, described beneath.

K&R introduced several language features:

Standard I/O library
long int data type
unsigned int data blazon
Compound consignment 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=-10, which had been interpreted as i =- ten (decrement i past 10) instead of the perhaps intended i = -10 (permit i exist −x).

Even afterward the publication of the 1989 ANSI standard, for many years K&R C was yet considered the "everyman common denominator" to which C programmers restricted themselves when maximum portability was desired, since many older compilers were yet in use, and because advisedly written M&R C code can be legal Standard C also.

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

For example:

                        long                                    some_function            ();                        /* int */                                    other_function            ();                        /* int */                                    calling_function            ()                        {                                                long                                    test1            ;                                                register                                    /* int */                                    test2            ;                                                test1                                    =                                    some_function            ();                                                if                                    (            test1                                    >                                    ane            )                                                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 on standards.

Since One thousand&R function declarations did not include whatever data virtually function arguments, part parameter type checks were not performed, although some compilers would issue a warning message if a local part was chosen with the wrong number of arguments, or if multiple calls to an external function used different numbers or types of arguments. Dissever tools such as Unix's lint utility were adult that (amid other things) could bank check for consistency of function utilise across multiple source files.

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

void functions (i.e., functions with no render value)
functions returning struct or wedlock types (rather than pointers)
assignment for struct information types
enumerated types

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

ANSI C and ISO C [edit]

During the tardily 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 institute a standard specification of C. X3J11 based the C standard on the Unix implementation; however, the non-portable portion of the Unix C library was handed off to the IEEE working group 1003 to become the footing for the 1988 POSIX standard. In 1989, the C standard was ratified every bit ANSI X3.159-1989 "Programming Language C". This version of the linguistic communication 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 Organization for Standardization (ISO) equally ISO/IEC 9899:1990, which is sometimes called C90. Therefore, the terms "C89" and "C90" refer to the aforementioned 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 within a year of ISO publication.

One of the aims of the C standardization process was to produce a superset of 1000&R C, incorporating many of the later on introduced unofficial features. The standards committee too included several additional features such as function prototypes (borrowed from C++), void pointers, support for international graphic symbol sets and locales, and preprocessor enhancements. Although the syntax for parameter declarations was augmented to include the way used in C++, the Thousand&R interface connected to exist permitted, for compatibility with existing source lawmaking.

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

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

Afterwards the ANSI/ISO standardization process, the C language specification remained relatively static for several years. In 1995, Normative Amendment ane to the 1990 C standard (ISO/IEC 9899/AMD1:1995, known informally as C95) was published, to correct some details and to add together more all-encompassing support for international graphic symbol sets.^[18]

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 commonly referred to equally "C99". It has since been amended 3 times by Technical Corrigenda.^[19]

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 point, support for variadic macros (macros of variable arity), and support for one-line comments beginning with //, as in BCPL or C++. Many of these had already been implemented as extensions in several C compilers.

C99 is for the most role backward compatible with C90, just is stricter in some ways; in particular, a declaration that lacks a type specifier no longer has int implicitly assumed. A standard macro __STDC_VERSION__ is defined with value 199901L to indicate that C99 support is available. GCC, Solaris Studio, and other C compilers now back up many or all of the new features of C99. The C compiler in Microsoft Visual C++, even so, implements the C89 standard and those parts of C99 that are required for compatibility with C++11.^[20] ^{[ needs update ]}

In addition, back up for Unicode identifiers (variable / role names) in the course of escaped characters (eastward.g. \U0001f431) is now required. Back up for raw Unicode names is optional.

C11 [edit]

In 2007, piece of 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, bearding structures, improved Unicode support, atomic operations, multi-threading, and bounds-checked functions. It as well makes some portions of the existing C99 library optional, and improves compatibility with C++. The standard macro __STDC_VERSION__ is defined as 201112L to signal that C11 back up is available.

C17 [edit]

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

C2x [edit]

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

Embedded C [edit]

Historically, embedded C programming requires nonstandard extensions to the C language in order to support exotic features such as fixed-point arithmetic, multiple distinct memory banks, and basic I/O operations.

In 2008, the C Standards Committee published a technical report extending the C language^[22] to address these problems by providing a common standard for all implementations to adhere to. Information technology includes a number of features not available in normal C, such as fixed-point 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 not significant in C; withal, line boundaries practise have significance during the preprocessing phase. Comments may announced either between the delimiters /* and */, or (since C99) following // until the finish of the line. Comments delimited past /* and */ do not nest, and these sequences of characters are not interpreted equally comment delimiters if they announced within string or character literals.^[24]

C source files contain declarations and function definitions. Office definitions, in turn, contain declarations and statements. Declarations either define new types using keywords such every bit struct, union, and enum, or assign types to and possibly reserve storage for new variables, unremarkably by writing the blazon followed by the variable proper name. Keywords such equally char and int specify built-in types. Sections of lawmaking are enclosed in braces ({ and }, sometimes chosen "curly brackets") to limit the scope of declarations and to act as a single argument for control structures.

Every bit an imperative language, C uses statements to specify actions. The near mutual statement is an expression statement, consisting of an expression to exist evaluated, followed by a semicolon; as a side effect of the evaluation, functions may be called and variables may be assigned new values. To change the normal sequential execution of statements, C provides several control-menses statements identified by reserved keywords. Structured programming is supported past if … [else] conditional execution and past do … while, while, and for iterative execution (looping). The for argument has separate initialization, testing, and reinitialization expressions, whatever or all of which tin exist omitted. break and continue can be used to leave the innermost enclosing loop statement or skip to its reinitialization. There is too a non-structured goto statement which branches direct to the designated characterization within the function. switch selects a case to be executed based on the value of an integer expression.

Expressions tin can employ a variety of built-in operators and may contain function calls. The order in which arguments to functions and operands to most operators are evaluated is unspecified. The evaluations may even be interleaved. However, all side effects (including storage to variables) volition occur earlier the next "sequence betoken"; sequence points include the end of each expression argument, and the entry to and return from each function call. Sequence points likewise occur during evaluation of expressions containing sure operators (&&, ||, ?: and the comma operator). This permits a high degree of object code optimization by the compiler, but requires C programmers to have 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 accept the incorrect precedence; some parts of the syntax could be better."^[25] The C standard did not try to correct many of these blemishes, because of the impact of such changes on already existing software.

Character set up [edit]

The bones C source grapheme set includes the following characters:

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

Newline indicates the end of a text line; it need non stand for to an bodily unmarried graphic symbol, although for convenience C treats it every bit one.

Additional multi-byte encoded characters may be used in cord literals, but they are non 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 bones C execution graphic symbol ready contains the aforementioned characters, along with representations for alert, backspace, and carriage return. Run-time support for extended graphic symbol sets has increased with each revision of the C standard.

Reserved words [edit]

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

auto
interruption
case
char
const
go on
default
exercise
double
else
enum
extern
float
for
goto
if
int
long
register
render
curt
signed
sizeof
static
struct
switch
typedef
marriage
unsigned
void
volatile
while

C99 reserved v more words:

_Bool
_Complex
_Imaginary
inline
restrict

C11 reserved seven more than words:^[26]

_Alignas
_Alignof
_Atomic
_Generic
_Noreturn
_Static_assert
_Thread_local

Most of the recently reserved words begin with an underscore followed by a uppercase letter, because identifiers of that course were previously reserved past the C standard for utilize simply past implementations. Since existing program source code should non have been using these identifiers, information technology would not be affected when C implementations started supporting these extensions to the programming language. Some standard headers do define more user-friendly synonyms for underscored identifiers. The language previously included a reserved word called entry, simply this was seldom implemented, and has at present 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: !, &&, ||
provisional 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 bespeak assignment, following the precedent of Fortran and PL/I, simply unlike ALGOL and its derivatives. C uses the operator == to test for equality. The similarity between these two operators (assignment and equality) may result in the accidental use of one in place of the other, and in many cases, the mistake does not produce an error message (although some compilers produce warnings). For case, the provisional expression if (a == b + 1) might mistakenly be written as if (a = b + 1), which will be evaluated as truthful if a is not nothing later on 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 every bit x & 1 == 0, which must be written equally (x & 1) == 0 if that is the coder's intent.^[29]

"Hullo, earth" example [edit]

The "hello, world" example, which appeared in the start edition of G&R, has become the model for an introductory plan in virtually programming textbooks. The program prints "hello, world" to the standard output, which is usually a terminal or screen display.

The original version was:^[30]

                        principal            ()                        {                                                printf            (            "hello, globe            \n            "            );                        }

A standard-befitting "how-do-you-do, globe" plan is:^[a]

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

The first line of the plan contains a preprocessing directive, indicated by #include. This causes the compiler to supervene upon 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 betoken that stdio.h is located using a search strategy that prefers headers provided with the compiler to other headers having the same name, every bit opposed to double quotes which typically include local or project-specific header files.

The next line indicates that a function named main is existence defined. The main function serves a special purpose in C programs; the run-time environs calls the principal function to brainstorm program execution. The type specifier int indicates that the value that is returned to the invoker (in this case the run-fourth dimension surroundings) equally 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 brace indicates the beginning of the definition of the master function.

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

The closing curly brace indicates the terminate of the code for the main function. According to the C99 specification and newer, the principal function, unlike any other function, 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-fourth dimension system as an exit code indicating successful execution.^[31]

Data types [edit]

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

C is often used in low-level systems programming where escapes from the type system may be necessary. The compiler attempts to ensure type correctness of virtually expressions, merely the programmer can override the checks in various ways, either by using a type cast to explicitly convert a value from one type to another, or by using pointers or unions to reinterpret the underlying bits of a data object in another style.

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

C's usual arithmetic conversions permit for efficient lawmaking to be generated, but tin can sometimes produce unexpected results. For case, a comparing of signed and unsigned integers of equal width requires a conversion of the signed value to unsigned. This tin can generate unexpected results if the signed value is negative.

Pointers [edit]

C supports the use of pointers, a blazon of reference that records the address or location of an object or function in memory. Pointers tin can exist dereferenced to access data stored at the address pointed to, or to invoke a pointed-to function. Pointers tin can exist manipulated using consignment or pointer arithmetic. The run-fourth dimension representation of a arrow value is typically a raw retention address (possibly augmented by an starting time-within-give-and-take field), only since a pointer'southward type includes the type of the affair pointed to, expressions including pointers can be blazon-checked at compile time. Arrow arithmetic is automatically scaled by the size of the pointed-to data type. Pointers are used for many purposes in C. Text strings are ordinarily manipulated using pointers into arrays of characters. Dynamic memory allocation is performed using pointers. Many data types, such as trees, are commonly implemented equally dynamically allocated struct objects linked together using pointers. Pointers to functions are useful for passing functions as arguments to higher-social club functions (such as qsort or bsearch) or equally callbacks to be invoked by event handlers.^[31]

A cipher pointer value explicitly points to no valid location. Dereferencing a null pointer value is undefined, oftentimes resulting in a segmentation mistake. Null pointer values are useful for indicating special cases such every bit no "next" pointer in the final node of a linked list, or as an error indication from functions returning pointers. In advisable contexts in source code, such every bit for assigning to a pointer variable, a null pointer constant can exist written as 0, with or without explicit casting to a arrow type, or as the NULL macro divers past several standard headers. In provisional contexts, zilch pointer values evaluate to imitation, while all other arrow values evaluate to true.

Void pointers (void *) point to objects of unspecified type, and can therefore be used as "generic" data pointers. Since the size and blazon of the pointed-to object is not known, void pointers cannot be dereferenced, nor is pointer arithmetic on them immune, although they tin can easily exist (and in many contexts implicitly are) converted to and from whatever other object pointer type.^[31]

Devil-may-care use of pointers is potentially dangerous. Because they are typically unchecked, a pointer variable can be fabricated to betoken to any capricious location, which can crusade undesirable effects. Although properly used pointers point to rubber places, they can be fabricated to point to unsafe places by using invalid pointer arithmetic; the objects they indicate to may go along to be used after 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, 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. Some other programming languages address these issues by 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 contempo C99 standard also allows a form of variable-length arrays. However, information technology is also possible to classify a block of memory (of arbitrary size) at run-time, using the standard library'due south malloc function, and treat information technology every bit an assortment.

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

C does not have a special provision for declaring multi-dimensional arrays, but rather relies on recursion within the type system to declare arrays of arrays, which finer accomplishes the aforementioned affair. The index values of the resulting "multi-dimensional assortment" tin can exist thought of as 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 job. However, in early versions of C the premises of the assortment must be known fixed values or else explicitly passed to whatsoever subroutine that requires them, and dynamically sized arrays of arrays cannot be accessed using double indexing. (A workaround for this was to allocate the array with an boosted "row vector" of pointers to the columns.) C99 introduced "variable-length arrays" which accost this effect.

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

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

Array–arrow interchangeability [edit]

The subscript notation x[i] (where x designates a pointer) is syntactic sugar for *(x+i).^[36] Taking advantage of the compiler'due south knowledge of the arrow type, the address that x + i points to is non the base address (pointed to by x) incremented by i bytes, simply rather is defined to be the base address incremented by i multiplied by the size of an element that x points to. Thus, x[i] designates the i+1th chemical element of the assortment.

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

The full size of an array x can be determined by applying sizeof to an expression of assortment blazon. The size of an element can be determined past applying the operator sizeof to whatever dereferenced element of an assortment A, as in due north = sizeof A[0]. This, the number of elements in a declared array A tin can be adamant as sizeof A / sizeof A[0]. Note, that if but a pointer to the first element is available as it is oftentimes the case in C code because of the automatic conversion described to a higher place, the information about the full type of the array and its length are lost.

Retention management [edit]

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

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

These three approaches are advisable in different situations and have various trade-offs. For example, static memory allocation has little allotment overhead, automated allocation may involve slightly more overhead, and dynamic retentiveness allocation tin can potentially take a great bargain of overhead for both allotment and deallocation. The persistent nature of static objects is useful for maintaining state information across office calls, automatic allotment is like shooting fish in a barrel to use but stack space is typically much more express and transient than either static memory or heap space, and dynamic memory allocation allows convenient allocation of objects whose size is known just at run-time. Most C programs make extensive utilise of all iii.

Where possible, automated or static allocation is commonly simplest considering the storage is managed by the compiler, freeing the programmer of the potentially error-prone chore of manually allocating and releasing storage. Nonetheless, many data structures can change in size at runtime, and since static allocations (and automated allocations before C99) must accept a stock-still size at compile-fourth dimension, there are many situations in which dynamic allocation is necessary.^[31] Prior to the C99 standard, variable-sized arrays were a mutual example of this. (Meet the article on malloc for an example of dynamically allocated arrays.) Unlike automatic allotment, which can fail at run time with uncontrolled consequences, the dynamic allocation functions return an indication (in the form of a nil pointer value) when the required storage cannot be allocated. (Static allocation that is too large is usually detected by the linker or loader, before the program can even begin 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 take indeterminate values (typically, any bit design happens to be present in the storage, which might not fifty-fifty represent a valid value for that type). If the program attempts to admission an uninitialized value, the results are undefined. Many modern compilers endeavor to detect and warn almost this problem, but both simulated positives and false negatives can occur.

Heap retentiveness allotment has to be synchronized with its actual usage in any programme to be reused as much equally possible. For example, if the only pointer to a heap memory allocation goes out of scope or has its value overwritten before it is deallocated explicitly, and so that memory cannot exist recovered for after reuse and is essentially lost to the program, a phenomenon known as a memory leak. Conversely, it is possible for memory to exist 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 it hard to diagnose the failure. Such issues are ameliorated in languages with automatic garbage collection.

Libraries [edit]

The C programming language uses libraries as its main method of extension. In C, a library is a fix of functions independent within 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 guild for a programme 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 (e.g., -lm, autograph for "link the math library").^[31]

The most common 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 separate standard headers (for instance, stdio.h) specify the interfaces for these and other standard library facilities.

Another common prepare 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 diverse standards such as POSIX and the Unmarried UNIX Specification.

Since many programs take been written in C, there are a broad variety of other libraries available. Libraries are often written in C because C compilers generate efficient object code; programmers then create interfaces to the library then that the routines can be used from higher-level languages like Coffee, Perl, and Python.^[31]

File handling and streams [edit]

File input and output (I/O) is non office of the C language itself simply instead is handled by libraries (such as the C standard library) and their associated header files (e.one thousand. stdio.h). File handling is mostly 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 memory area or queue) is temporarily used to store data before it'southward sent to the final destination. This reduces the fourth dimension spent waiting for slower devices, for instance a hard bulldoze or solid state drive. Depression-level I/O functions are not part of the standard C library^{[ clarification needed ]} but are more often than not part of "blank metal" programming (programming that's contained of any operating arrangement 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 help C programmers find and set up statements with undefined behavior or possibly erroneous expressions, with greater rigor than that provided past 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 be, such equally Lint. A mutual exercise is to use Lint to observe questionable code when a program is kickoff written. In one case a program passes Lint, it is then compiled using the C compiler. Also, many compilers can optionally warn most syntactically valid constructs that are likely to really be errors. MISRA C is a proprietary fix of guidelines to avoid such questionable code, developed for embedded systems.^[37]

There are also compilers, libraries, and operating system level mechanisms for performing deportment that are non a standard function of C, such as bounds checking for arrays, detection of buffer overflow, serialization, dynamic retentiveness tracking, and automatic garbage collection.

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

Uses [edit]

The C Programming Language

C is widely used for systems programming in implementing operating systems and embedded organisation applications,^[38] considering C lawmaking, when written for portability, tin can exist used for most purposes, yet when needed, system-specific code tin be used to admission specific hardware addresses and to perform type punning to match externally imposed interface requirements, with a depression run-fourth dimension demand on system resources.

C can be used for website programming using the Common Gateway Interface (CGI) equally a "gateway" for information between the Spider web application, the server, and the browser.^[39] C is oft called over interpreted languages considering of its speed, stability, and virtually-universal availability.^[40]

A consequence of C'southward broad availability and efficiency is that compilers, libraries and interpreters of other programming languages are frequently 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 information structures, because the layer of abstraction from hardware is thin, and its overhead is low, an of import benchmark for computationally intensive programs. For example, the GNU Multiple Precision Arithmetic Library, the GNU Scientific Library, Mathematica, and MATLAB are completely or partially written in C.

C is sometimes used as an intermediate language by implementations of other languages. This approach may be used for portability or convenience; by using C as an intermediate language, boosted machine-specific lawmaking generators are not 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 lawmaking. However, some of C's shortcomings have prompted the evolution of other C-based languages specifically designed for utilize equally intermediate languages, such every bit C--.

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

[edit]

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

C has both directly and indirectly influenced many later languages such as C#, D, Go, Java, JavaScript, Limbo, LPC, Perl, PHP, Python, and Unix's C vanquish.^[42] The virtually 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 programme structures that differ from those of C, sometimes radically.

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

When object-oriented programming languages became popular, C++ and Objective-C were two dissimilar 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 then compiled with a C compiler.^[43]

The C++ programming language (originally named "C with Classes") was devised by Bjarne Stroustrup every bit 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. Nearly a superset of C, C++ at present supports nearly of C, with a few exceptions.

Objective-C was originally a very "thin" layer on meridian 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, function declarations, and function calls is inherited from C, while the syntax for object-oriented features was originally taken from Smalltalk.

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

Come across also [edit]

Compatibility of C and C++
Comparison of Pascal and C
Comparison of programming languages
International Obfuscated C Lawmaking Competition
List of C-based programming languages
Listing of C compilers

Notes [edit]

^ The original example code will compile on almost mod compilers that are not in strict standard compliance mode, simply 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 primary office actually has two arguments, int argc and char *argv[], respectively, which can be used to handle command line arguments. The ISO C standard (section 5.1.ii.2.1) requires both forms of main to be supported, which is special treatment not afforded to whatsoever other function.

References [edit]

^ ^a ^b Kernighan, Brian W.; Ritchie, Dennis G. (February 1978). The C Programming Language (1st ed.). Englewood Cliffs, NJ: Prentice Hall. ISBN978-0-thirteen-110163-0.
^ Ritchie (1993): "Thompson had made a brief attempt to produce a system coded in an early on version of C—before structures—in 1972, but gave up the endeavor."
^ Fruderica (December xiii, 2020). "History of C". The cppreference.com. Archived from the original on October 24, 2020. Retrieved Oct 24, 2020.
^ Ritchie (1993): "The scheme of type limerick adopted past C owes considerable debt to Algol 68, although it did not, perhaps, emerge in a course that Algol's adherents would corroborate of."
^ Ring Team (October 23, 2021). "The Ring programming language and other languages". band-lang.net.
^ ^a ^b "Verilog HDL (and C)" (PDF). The Research Schoolhouse of Computer Science at the Australian National University. June 3, 2010. Archived from the original (PDF) on November 6, 2013. Retrieved Baronial nineteen, 2013. 1980s: ; Verilog outset introduced ; Verilog inspired by the C programming language
^ ^a ^b ^c ^d ^e Ritchie (1993)
^ "Programming Linguistic communication Popularity". 2009. Archived from the original on January 16, 2009. Retrieved Jan 16, 2009.
^ "TIOBE Programming Community Alphabetize". 2009. Archived from the original on May 4, 2009. Retrieved May half-dozen, 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 December 12, 2019. Retrieved September 10, 2019.
^ ^a ^b Johnson, S. C.; Ritchie, D. M. (1978). "Portability of C Programs and the UNIX System". Bell System Tech. J. 57 (half-dozen): 2021–2048. CiteSeerX10.1.ane.138.35. doi:10.1002/j.1538-7305.1978.tb02141.ten. S2CID 17510065. (Notation: The PDF is an OCR scan of the original, and contains a rendering of "IBM 370" equally "IBM 310".)
^ McIlroy, M. D. (1987). A Inquiry Unix reader: annotated excerpts from the Programmer's Manual, 1971–1986 (PDF) (Technical report). CSTR. Bell Labs. p. 10. 139. Archived (PDF) from the original on November 11, 2017. Retrieved February 1, 2015.
^ "C manual pages". FreeBSD Miscellaneous Data Manual (FreeBSD 13.0 ed.). May 30, 2011. Archived from the original on January 21, 2021. Retrieved January 15, 2021. [1] Archived January 21, 2021, at the Wayback Motorcar
^ Kernighan, Brian W.; Ritchie, Dennis M. (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 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 two, 2011.
^ Andrew Binstock (October 12, 2011). "Interview with Herb Sutter". Dr. Dobbs. Archived from the original on August 2, 2013. Retrieved September seven, 2013.
^ "Revised C23 Schedule WG 14 Due north 2759" (PDF). world wide web.open-std.org. Archived (PDF) from the original on June 24, 2021. Retrieved October 10, 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 Manual (fifth 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 Draft" (PDF). Archived (PDF) from the original on December 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. 20. ISBN978-1-58961-237-two. Archived from the original on July 29, 2020. Retrieved February 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). "Comparing of the Programming Languages C and Pascal". ACM Calculating Surveys. 14 (ane): 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 Jan vii, 2007. Retrieved August 5, 2012.
^ เอี่ยมสิริวงศ์, โอภาศ (2016). Programming with C. Bangkok, Thailand: SE-Instruction PUBLIC Visitor LIMITED. pp. 225–230. ISBN978-616-08-2740-4.
^ Raymond, Eric S. (October 11, 1996). The New Hacker's Dictionary (tertiary ed.). MIT Press. p. 432. ISBN978-0-262-68092-9. Archived from the original on Nov 12, 2012. Retrieved August 5, 2012.
^ "Man Page for lint (freebsd Section 1)". unix.com. May 24, 2001. Retrieved July 15, 2014.
^ Dale, Nell B.; Weems, Chip (2014). Programming and problem solving with C++ (6th ed.). Burlington, MA: Jones & Bartlett Learning. ISBN978-1449694289. OCLC 894992484.
^ Dr. Dobb'due south Sourcebook. U.S.A.: Miller Freeman, Inc. November–Dec 1995.
^ "Using C for CGI Programming". linuxjournal.com. March 1, 2005. Archived from the original on February xiii, 2010. Retrieved Jan 4, 2010.
^ McMillan, Robert (August 1, 2013). "Is Java Losing Its Mojo?". Wired. Archived from the original on February 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, U.s., October 2-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 two, 2019. Retrieved June 9, 2011.

Sources [edit]

Ritchie, Dennis 1000. (March 1993). "The Development of the C Linguistic communication". ACM SIGPLAN Notices. ACM. 28 (3): 201–208. doi:x.1145/155360.155580.
Ritchie, Dennis Grand. (1993). "The Development of the C Language". The Second ACM SIGPLAN Conference on History of Programming Languages (HOPL-II). ACM. pp. 201–208. doi:ten.1145/154766.155580. ISBN0-89791-570-four . Retrieved November 4, 2014.
Kernighan, Brian W.; Ritchie, Dennis Thou. (1996). The C Programming Language (2nd ed.). Prentice Hall. ISBNseven-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). (iii.61 MB)
comp.lang.c Frequently Asked Questions
A History of C, by Dennis Ritchie

dunbarhishattly.blogspot.com

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