View source for C syntax

{{Short description|Set of rules defining correctly structured programs}}
{{mi|
}}
[[File:C Hello World Program.png|thumb|300px|A snippet of [[C (programming language)|C]] code which prints "Hello, World!"]]

The '''[[Syntax (programming languages)|syntax]] of the [[C (programming language)|C programming language]]''' is the set of rules governing writing of software in C. It is designed to allow for programs that are extremely terse, have a close relationship with the resulting [[Object code|object code]], and yet provide relatively high-level data abstraction. C was the first widely successful high-level language for portable [[Operating system|operating-system]] development.

C [[Syntax (programming languages)|syntax]] makes use of the [[Maximal munch|maximal munch]] principle.

==Data structures==
{{main|C data types}}

===Primitive data types===
The C programming language represents numbers in three forms: ''[[Integer (computer science)|integral]]'', ''[[Real data type|real]]'' and ''[[Complex data type|complex]]''. This distinction reflects similar distinctions in the instruction set architecture of most [[Central processing unit|central processing unit]]s. ''Integral'' data types store numbers in the set of integers, while ''real'' and ''complex'' numbers represent numbers (or pair of numbers) in the set of real numbers in floating point form.

All C integer types have {{code|signed}} and {{code|unsigned}} variants. If {{code|signed}} or {{code|unsigned}} is not specified explicitly, in most circumstances, {{code|signed}} is assumed. However, for historic reasons, plain {{code|char}} is a type distinct from both {{code|signed char}} and {{code|unsigned char}}. It may be a signed type or an unsigned type, depending on the compiler and the character set (C guarantees that members of the C basic character set have positive values). Also, bit field types specified as plain {{code|int}} may be signed or unsigned, depending on the compiler.

====Integer types====
C's integer types come in different fixed sizes, capable of representing various ranges of numbers. The type {{code|char}} occupies exactly one [[Byte|byte]] (the smallest addressable storage unit), which is typically 8 bits wide. (Although {{code|char}} can represent any of C's "basic" characters, a wider type may be required for international character sets.) Most integer types have both [[Signedness|signed and unsigned]] varieties, designated by the {{code|signed}} and {{code|unsigned}} keywords. Signed integer types may use a [[Two's complement|two's complement]], [[Ones' complement|ones' complement]], or sign-and-magnitude [[Signed number representations|representation]]. In many cases, there are multiple equivalent ways to designate the type; for example, {{code|signed short int}} and {{code|short}} are synonymous.

The representation of some types may include unused "padding" bits, which occupy storage but are not included in the width. The following table provides a complete list of the standard integer types and their ''minimum'' allowed widths (including any sign bit).
{| class="wikitable"
|+ Specifications for standard integer types
|-
! Shortest form of specifier !! Minimum width (bits)
|-
| {{code|_Bool}}
| style="text-align: center" | 1
|-
| {{code|char}}
| style="text-align: center" | 8
|-
| {{code|signed char}}
| style="text-align: center" | 8
|-
| {{code|unsigned char}}
| style="text-align: center" | 8
|-
| {{code|short}}
| style="text-align: center" | 16
|-
| {{code|unsigned short}}
| style="text-align: center" | 16
|-
| {{code|int}}
| style="text-align: center" | 16
|-
| {{code|unsigned int}}
| style="text-align: center" | 16
|-
| {{code|long}}
| style="text-align: center" | 32
|-
| {{code|unsigned long}}
| style="text-align: center" | 32
|-
| {{code|long long}}<ref group="note" name="long long">The {{code|long long}} modifier was introduced in the [[C99]] standard.</ref>
| style="text-align: center" | 64
|-
| {{code|unsigned long long}}<ref group="note" name="long long"/>

| style="text-align: center" | 64
|}

The {{code|char}} type is distinct from both {{code|signed char}} and {{code|unsigned char}}, but is guaranteed to have the same representation as one of them. The {{code|_Bool}} and {{code|long long}} types are standardized since 1999, and may not be supported by older C compilers. Type {{code|_Bool}} is usually accessed via the <code>[[Typedef|typedef]]</code> name {{code|bool}} defined by the standard header <code>stdbool.h</code>.

In general, the widths and representation scheme implemented for any given platform are chosen based on the machine architecture, with some consideration given to the ease of importing source code developed for other platforms. The width of the {{code|int}} type varies especially widely among C implementations; it often corresponds to the most "natural" word size for the specific platform. The standard header limits.h defines macros for the minimum and maximum representable values of the standard integer types as implemented on any specific platform.

In addition to the standard integer types, there may be other "extended" integer types, which can be used for {{code|typedef}}s in standard headers. For more precise specification of width, programmers can and should use {{code|typedef}}s from the standard header stdint.h.

Integer constants may be specified in source code in several ways. Numeric values can be specified as [[Decimal|decimal]] (example: {{code|1022}}), [[Octal|octal]] with zero ({{code|0}}) as a prefix ({{code|01776}}), or [[Hexadecimal|hexadecimal]] with {{code|0x}} (zero x) as a prefix ({{code|0x3FE}}). A character in single quotes (example: {{code|'R'}}), called a "character constant," represents the value of that character in the execution character set, with type {{code|int}}. Except for character constants, the type of an integer constant is determined by the width required to represent the specified value, but is always at least as wide as {{code|int}}. This can be overridden by appending an explicit length and/or signedness modifier; for example, {{code|12lu}} has type {{code|unsigned long}}. There are no negative integer constants, but the same effect can often be obtained by using a unary negation operator "{{code|-}}".

====Enumerated type====

The [[Enumerated type|enumerated type]] in C, specified with the {{code|enum}} keyword, and often just called an "enum" (usually pronounced  {{IPAc-en|'|i:|n|V|m}} {{respell|EE|num}} or {{IPAc-en|'|i:|n|u:|m}} {{respell|EE|noom}}), is a type designed to represent values across a series of named constants. Each of the enumerated constants has type {{code|int}}. Each {{code|enum}} type itself is compatible with {{code|char}} or a signed or unsigned integer type, but each implementation defines its own rules for choosing a type.

Some compilers warn if an object with enumerated type is assigned a value that is not one of its constants. However, such an object can be assigned any values in the range of their compatible type, and {{code|enum}} constants can be used anywhere an integer is expected. For this reason, {{code|enum}} values are often used in place of preprocessor {{code|#define}} directives to create named constants. Such constants are generally safer to use than macros, since they reside within a specific identifier namespace.

An enumerated type is declared with the {{code|enum}} specifier and an optional name (or ''tag'') for the enum, followed by a list of one or more constants contained within curly braces and separated by commas, and an optional list of variable names. Subsequent references to a specific enumerated type use the {{code|enum}} keyword and the name of the enum. By default, the first constant in an enumeration is assigned the value zero, and each subsequent value is incremented by one over the previous constant. Specific values may also be assigned to constants in the declaration, and any subsequent constants without specific values will be given incremented values from that point onward.
For example, consider the following declaration:

<source lang=C>enum colors { RED, GREEN, BLUE = 5, YELLOW } paint_color;</source>

This declares the {{code|enum colors}} type; the {{code|int}} constants {{code|RED}} (whose value is 0), {{code|GREEN}} (whose value is one greater than {{code|RED}}, 1), {{code|BLUE}} (whose value is the given value, 5), and {{code|YELLOW}} (whose value is one greater than {{code|BLUE}}, 6); and the {{code|enum colors}} variable {{code|paint_color}}. The constants may be used outside of the context of the {{code|enum}} (where any integer value is allowed), and values other than the constants may be assigned to {{code|paint_color}}, or any other variable of type {{code|enum colors}}.

====Floating point types====
The floating-point form is used to represent numbers with a fractional component. They do not, however, represent most rational numbers exactly; they are instead a close approximation. There are three types of real values, denoted by their specifiers: single precision ({{code|float}}), double precision ({{code|double}}), and double extended precision ({{code|long double}}). Each of these may represent values in a different form, often one of the IEEE floating-point formats.

{| class="wikitable" width="80%"
|+ Floating-point types
|-
! rowspan="2" | Type specifiers
! colspan="2" | Precision (decimal digits)
! colspan="2" | Exponent range
|-
! Minimum
! IEEE 754
! Minimum
! IEEE 754
|-
| {{code|float}}
| align="center" | 6
| align="center" | 7.2 (24 bits)
| align="center" | ±37
| align="center" | ±38 (8 bits)
|-
| {{code|double}}
| align="center" | 10
| align="center" | 15.9 (53 bits)
| align="center" | ±37
| align="center" | ±307 (11 bits)
|-
| {{code|long double}}
| align="center" | 10
| align="center" | 34.0 (113 bits)
| align="center" | ±37
| align="center" | ±4931 (15 bits)
|}

Floating-point constants may be written in decimal notation, e.g. {{code|1.23}}. Decimal scientific notation may be used by adding {{code|e}} or {{code|E}} followed by a decimal exponent, also known as E notation, e.g. {{code|1.23e2}} (which has the value 1.23 × 10<sup>2</sup> = 123.0). Either a decimal point or an exponent is required (otherwise, the number is parsed as an integer constant). Hexadecimal floating-point constants follow similar rules, except that they must be prefixed by {{code|0x}} and use {{code|p}} or {{code|P}} to specify a binary exponent, e.g. {{code|0xAp-2}} (which has the value 2.5, since A<sub>h</sub> × 2<sup>−2</sup> = 10 × 2<sup>−2</sup> = 10 ÷ 4). Both decimal and hexadecimal floating-point constants may be suffixed by {{code|f}} or {{code|F}} to indicate a constant of type {{code|float}}, by {{code|l}} (letter {{code|l}}) or {{code|L}} to indicate type {{code|long double}}, or left unsuffixed for a {{code|double}} constant.

The standard header file {{code|float.h}} defines the minimum and maximum values of the implementation's floating-point types {{code|float}}, {{code|double}}, and {{code|long double}}. It also defines other limits that are relevant to the processing of floating-point numbers.

====Storage class specifiers====
Every object has a storage class. This specifies most basically the storage ''duration,'' which may be static (default for global), automatic (default for local), or dynamic (allocated), together with other features (linkage and register hint).

{| class="wikitable"
|+ Storage classes
|-
! Specifiers
! Lifetime
! Scope
! Default initializer
|-
| {{code|auto}}
| Block (stack)
| Block
| Uninitialized
|-
| {{code|register}}
| Block (stack or CPU register)
| Block
| Uninitialized
|-
| {{code|static}}
| Program
| Block or compilation unit
| Zero
|-
| {{code|extern}}
| Program
| Global (entire program)
| Zero
|-
| {{code|_Thread_local}}
| Thread
| 
| 
|-
| ''(none)''<sup>1</sup>
| Dynamic (heap)
|
| Uninitialized (initialized to {{code|0}} if using {{code|calloc()}})
|}

:<sup>1</sup> Allocated and deallocated using the {{code|malloc()}} and {{code|free()}} library functions.

Variables declared within a [[Block (programming)|block]] by default have automatic storage, as do those explicitly declared with the [[Automatic variable|{{code|auto}}]]<ref group="note">The meaning of auto is a type specifier rather than a storage class specifier in C++0x</ref> or [[Register (keyword)|{{code|register}}]] storage class specifiers. The {{code|auto}} and {{code|register}} specifiers may only be used within functions and function argument declarations; as such, the {{code|auto}} specifier is always redundant. Objects declared outside of all blocks and those explicitly declared with the [[Static variable|{{code|static}}]] storage class specifier have static storage duration. Static variables are initialized to zero by default by the [[Compiler|compiler]].

Objects with automatic storage are local to the block in which they were declared and are discarded when the block is exited. Additionally, objects declared with the {{code|register}} storage class may be given higher priority by the compiler for access to registers; although the compiler may choose not to actually store any of them in a register. Objects with this storage class may not be used with the address-of ({{code|&}}) unary operator. Objects with static storage persist for the program's entire duration. In this way, the same object can be accessed by a function across multiple calls. Objects with allocated storage duration are created and destroyed explicitly with {{code|malloc}}, {{code|free}}, and related functions.

The [[External variable|{{code|extern}}]] storage class specifier indicates that the storage for an object has been defined elsewhere. When used inside a block, it indicates that the storage has been defined by a declaration outside of that block. When used outside of all blocks, it indicates that the storage has been defined outside of the compilation unit. The {{code|extern}} storage class specifier is redundant when used on a function declaration. It indicates that the declared function has been defined outside of the compilation unit.

The [[Thread-local storage|{{code| Thread local}}]] (<code>thread_local</code> in [[C++]], since [[C23 (C standard revision)|C23]], and in earlier versions of C if the header <code><threads.h></code> is included) storage class specifier, introduced in [[C11 (C standard revision)|C11]], is used to declare a thread-local variable. It can be combined with {{code|static}} or {{code|extern}} to determine linkage.

Note that storage specifiers apply only to functions and objects; other things such as type and enum declarations are private to the compilation unit in which they appear. Types, on the other hand, have qualifiers (see below).

====Type qualifiers====
{{main|Type qualifier}}
Types can be qualified to indicate special properties of their data. The type qualifier <code>[[Const (computer programming)|const]]</code> indicates that a value does not change once it has been initialized. Attempting to modify a <code>const</code> qualified value yields undefined behavior, so some C compilers store them in rodata or (for embedded systems) in [[Read-only memory|read-only memory]] (ROM). The type qualifier <code>[[Volatile (computer programming)|volatile]]</code> indicates to an [[Optimizing compiler|optimizing compiler]] that it may not remove apparently redundant reads or writes, as the value may change even if it was not modified by any expression or statement, or multiple writes may be necessary, such as for memory-mapped I/O.

===Incomplete types===
An incomplete type is a structure or union type whose members have not yet been specified, an array type whose dimension has not yet been specified, or the {{code|void}} type (the {{code|void}} type cannot be completed). Such a type may not be instantiated (its size is not known), nor may its members be accessed (they, too, are unknown); however, the derived pointer type may be used (but not dereferenced).

They are often used with pointers, either as forward or external declarations. For instance, code could declare an incomplete type like this:
<source lang=C>
struct thing *pt;
</source>
This declares {{code|pt}} as a pointer to {{code|struct thing}} ''and'' the incomplete type {{code|struct thing}}. Pointers to data always have the same byte-width regardless of what they point to, so this statement is valid by itself (as long as {{code|pt}} is not dereferenced). The incomplete type can be completed later in the same scope by redeclaring it:
<source lang=C>
struct thing {
    int num;
}; /* thing struct type is now completed */
</source>

Incomplete types are used to implement [[Recursion (computer science)|recursive]] structures; the body of the type declaration may be deferred to later in the translation unit:
<source lang=C>
typedef struct Bert Bert;
typedef struct Wilma Wilma;

struct Bert {
    Wilma *wilma;
};

struct Wilma {
    Bert *bert;
};
</source>

Incomplete types are also used for data hiding; the incomplete type is defined in a header file, and the body only within the relevant source file.

===Pointers===
In declarations the asterisk modifier ({{code|*}}) specifies a pointer type. For example, where the specifier {{code|int}} would refer to the integer type, the specifier {{code|int*}} refers to the type "pointer to integer". Pointer values associate two pieces of information: a memory address and a data type. The following line of code declares a pointer-to-integer variable called ''ptr'':

<source lang=C>int *ptr;</source>

====Referencing====
When a non-static pointer is declared, it has an unspecified value associated with it. The address associated with such a pointer must be changed by assignment prior to using it. In the following example, ''ptr'' is set so that it points to the data associated with the variable ''a'':

<source lang=C>
int a = 0;
int *ptr = &a;
</source>

In order to accomplish this, the "address-of" operator (unary {{code|&}}) is used. It produces the memory location of the data object that follows.

====Dereferencing====
The pointed-to data can be accessed through a pointer value. In the following example, the integer variable ''b'' is set to the value of integer variable ''a'', which is 10:

<source lang=C>
int a=10;
int *p;
p = &a;
int b = *p;
</source>

In order to accomplish that task, the unary [[Dereference operator|dereference operator]], denoted by an asterisk (*), is used. It returns the data to which its operand—which must be of pointer type—points. Thus, the expression *''p'' denotes the same value as ''a''. Dereferencing a [[Null pointer|null pointer]] is illegal.

===Arrays===

====Array definition====
Arrays are used in C to represent structures of consecutive elements of the same type. The definition of a (fixed-size) array has the following syntax:

<source lang=C>int array[100];</source>

which defines an array named ''array'' to hold 100 values of the primitive type {{code|int}}. If declared within a function, the array dimension may also be a non-constant expression, in which case memory for the specified number of elements will be allocated. In most contexts in later use, a mention of the variable ''array'' is converted to a pointer to the first item in the array. The [[Sizeof|{{code|sizeof}}]] operator is an exception: {{code|sizeof array}} yields the size of the entire array (that is, 100 times the size of an {{code|int}}, and {{code|sizeof(array) / sizeof(int)}} will return 100). Another exception is the & (address-of) operator, which yields a pointer to the entire array, for example

<source lang=C>int (*ptr_to_array)[100] = &array;</source>

====Accessing elements====
The primary facility for accessing the values of the elements of an array is the array subscript operator. To access the ''i''-indexed element of ''array'', the syntax would be {{code|array[i]}}, which refers to the value stored in that array element.

Array subscript numbering begins at 0 (see Zero-based indexing). The largest allowed array subscript is therefore equal to the number of elements in the array minus 1. To illustrate this, consider an array ''a'' declared as having 10 elements; the first element would be {{code|a[0]}} and the last element would be {{code|a[9]}}.

C provides no facility for automatic [[Bounds checking|bounds checking]] for array usage. Though logically the last subscript in an array of 10 elements would be 9, subscripts 10, 11, and so forth could accidentally be specified, with undefined results.

Due to arrays and pointers being interchangeable, the addresses of each of the array elements can be expressed in equivalent pointer arithmetic. The following table illustrates both methods for the existing array:

{| class="wikitable" style="margin-left: auto; margin-right: auto; text-align: center"
|+ Array subscripts vs. pointer arithmetic
! style="text-align: left" | Element
! First
! Second
! Third
! ''n''th
|-
! style="text-align: left" | Array subscript
| {{C-lang|array[0]}}
| {{C-lang|array[1]}}
| {{C-lang|array[2]}}
| {{C-lang|array[n - 1]}}
|-
! style="text-align: left" | Dereferenced pointer
| {{C-lang|*array}}
| {{C-lang|*(array + 1)}}
| {{C-lang|*(array + 2)}}
| {{C-lang|*(array + n - 1)}}
|}

Since the expression {{code|a[i]}} is semantically equivalent to {{code|*(a+i)}}, which in turn is equivalent to {{code|*(i+a)}}, the expression can also be written as {{code|i[a]}}, although this form is rarely used.

====Variable-length arrays====
[[C99]] standardised [[Variable-length array|variable-length array]]s (VLAs) within block scope. Such array variables are allocated based on the value of an integer value at runtime upon entry to a block, and are deallocated at the end of the block.<ref name="bk21st" /> As of [[C11 (C standard revision)|C11]] this feature is no longer required to be implemented by the compiler.

<source lang=C>
int n = ...;
int a[n];
a[3] = 10;
</source>

This syntax produces an array whose size is fixed until the end of the block.

====Dynamic arrays====
{{main|C dynamic memory allocation}}
Arrays that can be resized dynamically can be produced with the help of the [[C standard library]]. The <code>malloc</code> function provides a simple method for allocating memory. It takes one parameter: the amount of memory to allocate in bytes. Upon successful allocation, {{code|malloc}} returns a generic ({{code|void}}) pointer value, pointing to the beginning of the allocated space. The pointer value returned is converted to an appropriate type implicitly by assignment. If the allocation could not be completed, {{code|malloc}} returns a [[Null pointer|null pointer]]. The following segment is therefore similar in function to the above desired declaration:

<source lang=C>
#include <stdlib.h> /* declares malloc */
...
int *a = malloc(n * sizeof *a);
a[3] = 10;
</source>

The result is a "pointer to {{code|int}}" variable (''a'') that points to the first of ''n'' contiguous {{code|int}} objects; due to array–pointer equivalence this can be used in place of an actual array name, as shown in the last line. The advantage in using this dynamic allocation is that the amount of memory that is allocated to it can be limited to what is actually needed at run time, and this can be changed as needed (using the standard library function {{code|realloc}}).

When the dynamically allocated memory is no longer needed, it should be released back to the run-time system. This is done with a call to the {{code|free}} function. It takes a single parameter: a pointer to previously allocated memory. This is the value that was returned by a previous call to {{code|malloc}}.

As a security measure, some programmers {{who|date=August 2020}} then set the pointer variable to {{code|NULL}}:

<source lang=C>
free(a);
a = NULL;
</source>

This ensures that further attempts to dereference the pointer, on most systems, will crash the program. If this is not done, the variable becomes a [[Dangling pointer|dangling pointer]] which can lead to a use-after-free bug. However, if the pointer is a local variable, setting it to {{code|NULL}} does not prevent the program from using other copies of the pointer. Local use-after-free bugs are usually easy for static analyzers to recognize. Therefore, this approach is less useful for local pointers and it is more often used with pointers stored in long-living structs. In general though, setting pointers to {{code|NULL}} is good practice {{according to whom|date=August 2020}} as it allows a programmer to {{code|NULL}}-check pointers prior to dereferencing, thus helping prevent crashes.

Recalling the array example, one could also create a fixed-size array through dynamic allocation:

<source lang=C>
int (*a)[100] = malloc(sizeof *a);
</source>

...Which yields a pointer-to-array.

Accessing the pointer-to-array can be done in two ways:
<source lang=C>
(*a)[index];

index[*a];
</source>

Iterating can also be done in two ways:
<source lang=C>
for (int i = 0; i < 100; i++)
    (*a)[i];

for (int *i = a[0]; i < a[1]; i++)
    *i;
</source>

The benefit to using the second example is that the numeric limit of the first example isn't required, which means that the pointer-to-array could be of any size and the second example can execute without any modifications.

====Multidimensional arrays====
In addition, C supports arrays of multiple dimensions, which are stored in row-major order. Technically, C multidimensional arrays are just one-dimensional arrays whose elements are arrays. The syntax for declaring multidimensional arrays is as follows:
 <source lang=C>int array2d[ROWS][COLUMNS];</source>
where ''ROWS'' and ''COLUMNS'' are constants. This defines a two-dimensional array. Reading the subscripts from left to right, ''array2d'' is an array of length ''ROWS'', each element of which is an array of ''COLUMNS'' integers.

To access an integer element in this multidimensional array, one would use
 <source lang=C>array2d[4][3]</source>
Again, reading from left to right, this accesses the 5th row, and the 4th element in that row. The expression {{code|array2d[4]}} is an array, which we are then subscripting with [3] to access the fourth integer.

{| class="wikitable" style="margin-left: auto; margin-right: auto; text-align: center"
|+ Array subscripts vs. pointer arithmetic<ref>{{cite book|last=Balagurusamy|first=E|title=Programming in ANSI C|publisher=Tata McGraw Hill|pages=366}}</ref>
! style="text-align: left" | Element
! First
! Second row, second column
! ''i''th row, ''j''th column
|-
! style="text-align: left" | Array subscript
| {{C-lang|array[0][0]}}
| {{C-lang|array[1][1]}}
| {{C-lang|array[i - 1][j - 1]}}
|-
! style="text-align: left" | Dereferenced pointer
| {{C-lang|*(*(array + 0) + 0)}}
| {{C-lang|*(*(array + 1) + 1)}}
| {{C-lang|*(*(array + i - 1) + j - 1)}}
|}

Higher-dimensional arrays can be declared in a similar manner.

A multidimensional array should not be confused with an array of pointers to arrays (also known as an [[Iliffe vector]] or sometimes an ''array of arrays''). The former is always rectangular (all subarrays must be the same size), and occupies a contiguous region of memory. The latter is a one-dimensional array of pointers, each of which may point to the first element of a subarray in a different place in memory, and the sub-arrays do not have to be the same size. The latter can be created by multiple uses of {{code|malloc}}.

===Strings===
{{main | C string handling}}

In C, string literals are surrounded by double quotes ({{code|"}}) (e.g., {{code|"Hello world!"}}) and are compiled to an array of the specified {{code|char}} values with an additional null terminating character (0-valued) code to mark the end of the string.

[[String literal]]s may not contain embedded newlines; this proscription somewhat simplifies parsing of the language. To include a newline in a string, the backslash escape {{code|\n}} may be used, as below.

There are several standard library functions for operating with string data (not necessarily constant) organized as array of {{code|char}} using this null-terminated format; see below.

C's string-literal syntax has been very influential, and has made its way into many other languages, such as C++, Objective-C, Perl, Python, PHP, Java, JavaScript, C#, and Ruby. Nowadays, almost all new languages adopt or build upon C-style string syntax. Languages that lack this syntax tend to precede C.

====Backslash escapes====
{{main|Escape sequences in C}}
Because certain characters cannot be part of a literal string expression directly, they are instead identified by an escape sequence starting with a backslash ({{code|\}}). For example, the backslashes in {{code|"This string contains \"double quotes\"."}} indicate (to the compiler) that the inner pair of quotes are intended as an actual part of the string, rather than the default reading as a delimiter (endpoint) of the string itself.

Backslashes may be used to enter various control characters, etc., into a string:
{| class="wikitable"
! align="left" |Escape
! align="left" |Meaning
|-
| {{code|\\}} || Literal backslash
|-
| {{code|\"}} || Double quote
|-
| {{code|\'}} || Single quote
|-
| {{code|\n}} || Newline (line feed)
|-
| {{code|\r}} || Carriage return
|-
| {{code|\b}} || Backspace
|-
| {{code|\t}} || Horizontal tab
|-
| {{code|\f}} || Form feed
|-
| {{code|\a}} || Alert (bell)
|-
| {{code|\v}} || Vertical tab
|-
| {{code|\?}} || Question mark (used to escape trigraphs)
|-
| {{code|%%}} || Percentage mark, [[Software:Printf format string|printf format string]]s only (Note \% is non standard and is not always recognised)
|-
| <code>\''OOO''</code> || Character with octal value ''OOO'' (where ''OOO'' is 1-3 octal digits, '0'-'7')
|-
| <code>\x''HH''</code> || Character with hexadecimal value ''HH'' (where ''HH'' is 1 or more hex digits, '0'-'9','A'-'F','a'-'f')
|}

The use of other backslash escapes is not defined by the C standard, although compiler vendors often provide additional escape codes as language extensions. One of these is the escape sequence <code>\e</code> for the [[Escape character|escape character]] with ASCII hex value 1B which was not added to the C standard due to lacking representation in other character sets (such as [[Software:EBCDIC|EBCDIC]]). It is available in [[Software:GNU Compiler Collection|GCC]], [[Software:Clang|clang]] and [[Software:Tiny C Compiler|tcc]].

====String literal concatenation====
C has [[String literal concatenation|string literal concatenation]], meaning that adjacent string literals are concatenated at compile time; this allows long strings to be split over multiple lines, and also allows string literals resulting from [[C preprocessor]] defines and macros to be appended to strings at compile time:
<source lang=C>
    printf(__FILE__ ": %d: Hello "
           "world\n", __LINE__);
</source>
will expand to
<source lang=C>
    printf("helloworld.c" ": %d: Hello "
           "world\n", 10);
</source>
which is syntactically equivalent to
<source lang=C>
    printf("helloworld.c: %d: Hello world\n", 10);
</source>

====Character constants====
Individual character constants are single-quoted, e.g. {{code|'A'}}, and have type {{code|int}} (in C++, {{code|char}}). The difference is that {{code|"A"}} represents a null-terminated array of two characters, 'A' and '\0', whereas {{code|'A'}} directly represents the character value (65 if ASCII is used). The same backslash-escapes are supported as for strings, except that (of course) {{code|"}} can validly be used as a character without being escaped, whereas {{code|'}} must now be escaped.

A character constant cannot be empty (i.e. {{code|''}} is invalid syntax), although a string may be (it still has the null terminating character). Multi-character constants (e.g. {{code|'xy'}}) are valid, although rarely useful — they let one store several characters in an integer (e.g. 4 ASCII characters can fit in a 32-bit integer, 8 in a 64-bit one). Since the order in which the characters are packed into an {{code|int}} is not specified (left to the implementation to define), portable use of multi-character constants is difficult.

Nevertheless, in situations limited to a specific platform and the compiler implementation, multicharacter constants do find their use in specifying signatures. One common use case is the [[OSType]], where the combination of Classic Mac OS compilers and its inherent big-endianness means that bytes in the integer appear in the exact order of characters defined in the literal. The definition by popular "implementations" are in fact consistent: in GCC, Clang, and Visual C++, {{code|'1234'}} yields <code>0x3'''1'''3'''2'''3'''3'''3'''4'''</code> under ASCII.<ref>{{cite web |title=The C Preprocessor: Implementation-defined behavior |url=https://gcc.gnu.org/onlinedocs/cpp/Implementation-defined-behavior.html |website=gcc.gnu.org}}</ref><ref>{{cite web |title=String and character literals (C++) |url=https://docs.microsoft.com/en-us/cpp/cpp/string-and-character-literals-cpp?view=vs-2019#code-try-2 |website=Visual C++ 19 Documentation |access-date=20 November 2019 |language=en-us}}</ref>

Like string literals, character constants can also be modified by prefixes, for example {{code|L'A'}} has type {{code|wchar_t}} and represents the character value of "A" in the wide character encoding.

====Wide character strings====
Since type {{code|char}} is 1 byte wide, a single {{code|char}} value typically can represent at most 255 distinct character codes, not nearly enough for all the characters in use worldwide. To provide better support for international characters, the first C standard (C89) introduced [[Wide character|wide character]]s (encoded in type {{code|wchar_t}}) and wide character strings, which are written as {{code|L"Hello world!"}}

Wide characters are most commonly either 2 bytes (using a 2-byte encoding such as [[UTF-16]]) or 4 bytes (usually [[UTF-32]]), but Standard C does not specify the width for {{code|wchar_t}}, leaving the choice to the implementor. [[Software:Microsoft Windows|Microsoft Windows]] generally uses UTF-16, thus the above string would be 26 bytes long for a Microsoft compiler; the [[Software:Unix|Unix]] world prefers UTF-32, thus compilers such as GCC would generate a 52-byte string. A 2-byte wide {{code|wchar_t}} suffers the same limitation as {{code|char}}, in that certain characters (those outside the BMP) cannot be represented in a single {{code|wchar_t}}; but must be represented using surrogate pairs.

The original C standard specified only minimal functions for operating with wide character strings; in 1995 the standard was modified to include much more extensive support, comparable to that for {{code|char}} strings. The relevant functions are mostly named after their {{code|char}} equivalents, with the addition of a "w" or the replacement of "str" with "wcs"; they are specified in {{code|<wchar.h>}}, with {{code|<wctype.h>}} containing wide-character classification and mapping functions.

The now generally recommended method<ref group="note">see [[UTF-8]] first section for references</ref> of supporting international characters is through [[UTF-8]], which is stored in {{code|char}} arrays, and can be written directly in the source code if using a UTF-8 editor, because UTF-8 is a direct [[Extended ASCII|ASCII extension]].

====Variable width strings====
A common alternative to {{code|wchar_t}} is to use a [[Variable-width encoding|variable-width encoding]], whereby a logical character may extend over multiple positions of the string. Variable-width strings may be encoded into literals verbatim, at the risk of confusing the compiler, or using numerical backslash escapes (e.g. {{code|"\xc3\xa9"}} for "é" in UTF-8). The [[UTF-8]] encoding was specifically designed (under [[Software:Plan 9 from Bell Labs|Plan 9]]) for compatibility with the standard library string functions; supporting features of the encoding include a lack of embedded nulls, no valid interpretations for subsequences, and trivial resynchronisation. Encodings lacking these features are likely to prove incompatible with the standard library functions; encoding-aware string functions are often used in such cases.

====Library functions====
[[String (computer science)|Strings]], both constant and variable, can be manipulated without using the [[Standard library|standard library]]. However, the library contains many [[C string handling|useful functions]] for working with null-terminated strings.

===Structures and unions===

====Structures====
Structures and [[Union type|unions]] in C are defined as data containers consisting of a sequence of named members of various types. They are similar to records in other programming languages. The members of a structure are stored in consecutive locations in memory, although the compiler is allowed to insert padding between or after members (but not before the first member) for efficiency or as padding required for proper [[Data structure alignment|alignment]] by the target architecture. The size of a structure is equal to the sum of the sizes of its members, plus the size of the padding.

====Unions====
Unions in C are related to structures and are defined as objects that may hold (at different times) objects of different types and sizes. They are analogous to variant records in other programming languages. Unlike structures, the components of a union all refer to the same location in memory. In this way, a union can be used at various times to hold different types of objects, without the need to create a separate object for each new type. The size of a union is equal to the size of its largest component type.

====Declaration====
Structures are declared with the [[Struct (C programming language)|{{code|struct}}]] keyword and unions are declared with the {{code|union}} keyword. The specifier keyword is followed by an optional identifier name, which is used to identify the form of the structure or union. The identifier is followed by the declaration of the structure or union's body: a list of member declarations, contained within curly braces, with each declaration terminated by a semicolon. Finally, the declaration concludes with an optional list of identifier names, which are declared as instances of the structure or union.

For example, the following statement declares a structure named {{code|s}} that contains three members; it will also declare an instance of the structure known as {{code|tee}}:

<source lang=C>
struct s {
    int   x;
    float y;
    char  *z;
} tee;
</source>

And the following statement will declare a similar union named {{code|u}} and an instance of it named {{code|n}}:

<source lang=C>
union u {
    int   x;
    float y;
    char  *z;
} n;
</source>

Members of structures and unions cannot have an incomplete or function type. Thus members cannot be an instance of the structure or union being declared (because it is incomplete at that point) but can be pointers to the type being declared.

Once a structure or union body has been declared and given a name, it can be considered a new data type using the specifier {{code|struct}} or {{code|union}}, as appropriate, and the name. For example, the following statement, given the above structure declaration, declares a new instance of the structure {{code|s}} named {{code|r}}:

<source lang=C>struct s r;</source>

It is also common to use the <code>[[Typedef|typedef]]</code> specifier to eliminate the need for the {{code|struct}} or {{code|union}} keyword in later references to the structure. The first identifier after the body of the structure is taken as the new name for the structure type (structure instances may not be declared in this context). For example, the following statement will declare a new type known as ''s_type'' that will contain some structure:

<source lang=C>typedef struct {...} s_type;</source>

Future statements can then use the specifier ''s_type'' (instead of the expanded {{code|struct}} ... specifier) to refer to the structure.

====Accessing members====
Members are accessed using the name of the instance of a structure or union, a period ({{code|.}}), and the name of the member. For example, given the declaration of ''tee'' from above, the member known as ''y'' (of type {{code|float}}) can be accessed using the following syntax:

<source lang=C>tee.y</source>

Structures are commonly accessed through pointers. Consider the following example that defines a pointer to ''tee'', known as ''ptr_to_tee'':

<source lang=C>struct s *ptr_to_tee = &tee;</source>

Member ''y'' of ''tee'' can then be accessed by dereferencing ''ptr_to_tee'' and using the result as the left operand:

<source lang=C>(*ptr_to_tee).y</source>

Which is identical to the simpler {{code|tee.y}} above as long as ''ptr_to_tee'' points to ''tee''. Due to [[Operators in C and C++#Operator precedence|operator precedence]] ("." being higher than "*"), the shorter <code>*ptr_to_tee.y</code> is incorrect for this purpose, instead being parsed as <code>*(ptr_to_tee.y)</code> and thus the parentheses are necessary. Because this operation is common, C provides an [[Syntactic sugar|abbreviated syntax]] for accessing a member directly from a pointer. With this syntax, the name of the instance is replaced with the name of the pointer and the period is replaced with the character sequence {{code|->}}. Thus, the following method of accessing ''y'' is identical to the previous two:

<source lang=C>ptr_to_tee->y</source>

Members of unions are accessed in the same way.

This can be chained; for example, in a linked list, one may refer to <code>n->next->next</code> for the second following node (assuming that <code>n->next</code> is not null).

====Assignment====
Assigning values to individual members of structures and unions is syntactically identical to assigning values to any other object. The only difference is that the ''lvalue'' of the assignment is the name of the member, as accessed by the syntax mentioned above.

A structure can also be assigned as a unit to another structure of the same type. Structures (and pointers to structures) may also be used as function parameter and return types.

For example, the following statement assigns the value of 74 (the ASCII code point for the letter 't') to the member named ''x'' in the structure ''tee'', from above:

<source lang=C>tee.x = 74;</source>

And the same assignment, using ''ptr_to_tee'' in place of ''tee'', would look like:

<source lang=C>ptr_to_tee->x = 74;</source>

Assignment with members of unions is identical.

====Other operations====
According to the C standard, the only legal operations that can be performed on a structure are copying it, assigning to it as a unit (or initializing it), taking its address with the address-of ({{code|&}}) unary operator, and accessing its members. Unions have the same restrictions. One of the operations implicitly forbidden is comparison: structures and unions cannot be compared using C's standard comparison facilities ({{code|1===}}, {{code|>}}, {{code|<}}, etc.).

====Bit fields====
C also provides a special type of member known as a bit field, which is an integer with an explicitly specified number of bits. A bit field is declared as a structure (or union) member of type {{code|int}}, {{code|signed int}}, {{code|unsigned int}}, or {{code|_Bool}}<!-- Add _BitInt(N) when updating the page for C23 -->,<ref group="note">Other implementation-defined types are also allowed. C++ allows using all integral and enumerated types and a lot of C compilers do the same.</ref> following the member name by a colon ({{code|:}}) and the number of bits it should occupy. The total number of bits in a single bit field must not exceed the total number of bits in its declared type (this is allowed in C++ however, where the extra bits are used for padding).

As a special exception to the usual C syntax rules, it is implementation-defined whether a bit field declared as type {{code|int}}, without specifying {{code|signed}} or {{code|unsigned}}, is signed or unsigned. Thus, it is recommended to explicitly specify {{code|signed}} or {{code|unsigned}} on all structure members for portability.

Unnamed fields consisting of just a colon followed by a number of bits are also allowed; these indicate padding. Specifying a width of zero for an unnamed field is used to force [[Data structure alignment|alignment]] to a new word.<ref>Kernighan & Richie</ref>

The members of bit fields do not have addresses, and as such cannot be used with the address-of ({{code|&}}) unary operator. The {{code|sizeof}} operator may not be applied to bit fields.

The following declaration declares a new structure type known as {{code|f}} and an instance of it known as {{code|g}}. Comments provide a description of each of the members:

<source lang=C>
struct f {
    unsigned int  flag : 1;  /* a bit flag: can either be on (1) or off (0) */
    signed int    num  : 4;  /* a signed 4-bit field; range -7...7 or -8...7 */
    signed int         : 3;  /* 3 bits of padding to round out to 8 bits */
} g;
</source>

===Initialization===
Default initialization depends on the storage class specifier, described above.

Because of the language's grammar, a scalar initializer may be enclosed in any number of curly brace pairs. Most compilers issue a warning if there is more than one such pair, though.
<source lang=C>int x = 12;
int y = { 23 };     //Legal, no warning
int z = { { 34 } }; //Legal, expect a warning</source>

Structures, unions and arrays can be initialized in their declarations using an initializer list. Unless designators are used, the components of an initializer correspond with the elements in the order they are defined and stored, thus all preceding values must be provided before any particular element's value. Any unspecified elements are set to zero (except for unions). Mentioning too many initialization values yields an error.

The following statement will initialize a new instance of the structure ''s'' known as ''pi'':
<source lang=C>struct s {
    int   x;
    float y;
    char  *z;
};

struct s pi = { 3, 3.1415, "Pi" };</source>

====Designated initializers====
Designated initializers allow members to be initialized by name, in any order, and without explicitly providing the preceding values. The following initialization is equivalent to the previous one:
<source lang=C>struct s pi = { .z = "Pi", .x = 3, .y = 3.1415 };</source>

Using a designator in an initializer moves the initialization "cursor". In the example below, if <code>MAX</code> is greater than 10, there will be some zero-valued elements in the middle of <code>a</code>; if it is less than 10, some of the values provided by the first five initializers will be overridden by the second five (if <code>MAX</code> is less than 5, there will be a compilation error):
<source lang=C>int a[MAX] = { 1, 3, 5, 7, 9, [MAX-5] = 8, 6, 4, 2, 0 };</source>

In C89, a union was initialized with a single value applied to its first member. That is, the union ''u'' defined above could only have its ''int x'' member initialized:
<source lang=C>union u value = { 3 };</source>

Using a designated initializer, the member to be initialized does not have to be the first member:
<source lang=C>union u value = { .y = 3.1415 }; </source>

If an array has unknown size (i.e. the array was an incomplete type), the number of initializers determines the size of the array and its type becomes complete:
<source lang=C>
int x[] = { 0, 1, 2 } ;</source>

Compound designators can be used to provide explicit initialization when unadorned initializer lists
might be misunderstood. In the example below, <code>w</code> is declared as an array of structures, each structure consisting of a member <code>a</code> (an array of 3 <code>int</code>) and a member <code>b</code> (an <code>int</code>). The initializer sets the size of <code>w</code> to 2 and sets the values of the first element of each <code>a</code>:
<source lang=C>struct { int a[3], b; } w[] = { [0].a = {1}, [1].a[0] = 2 };</source><!--
Note: The [http://www.open-std.org/jtc1/sc22/wg14/www/docs/n1124.pdf C99 specification]'s grammar for designations reads in part:

designation:     designator-list =
designator-list: designator
                 designator-list designator
designator:      [ constant-expression ]
                 . identifier

...which can be understood as making these code fragments legal:
int x[] = { [1] [9] = 2 } ;
struct t
{
    char *name;
    char *nickname;
} who = { .name .nickname = "Unknown" };

But that is incorrect. The designators that make up the designator-list are *not* space-separated: the grammar means to describe the kind of structure-path given in the example.
-->
This is equivalent to:<source lang=C>struct { int a[3], b; } w[] =
{
   { { 1, 0, 0 }, 0 },
   { { 2, 0, 0 }, 0 } 
};</source>

There is no way to specify repetition of an initializer in standard C.

====Compound literals====

It is possible to borrow the initialization methodology to generate compound structure and array literals:

<source lang=C>
// pointer created from array literal.
int *ptr = (int[]){ 10, 20, 30, 40 };

// pointer to array.
float (*foo)[3] = &(float[]){ 0.5f, 1.f, -0.5f };

struct s pi = (struct s){ 3, 3.1415, "Pi" };
</source>

Compound literals are often combined with designated initializers to make the declaration more readable:<ref name="bk21st" />

<source lang=C>pi = (struct s){ .z = "Pi", .x = 3, .y = 3.1415 };</source>

==Operators==
{{main|Operators in C and C++}}

==Control structures==
C is a [[Free-form language|free-form language]].

Bracing style varies from [[Computer programming|programmer]] to programmer and can be the subject of debate. See Indent style for more details.

===Compound statements===
In the items in this section, any <statement> can be replaced with a '''compound statement'''. Compound statements have the form:
<source lang=C>
{
    <optional-declaration-list>
    <optional-statement-list>
}
</source>
and are used as the body of a function or anywhere that a single statement is expected. The declaration-list declares variables to be used in that scope, and the statement-list are the actions to be performed. Brackets define their own scope, and variables defined inside those brackets will be automatically
deallocated at the closing bracket. Declarations and statements can be freely intermixed within a compound statement (as in [[C++]]).

===Selection statements===
C has two types of selection statements: the {{code|if}} statement and the [[Switch statement|{{code|switch}} statement]].

The {{code|if}} statement is in the form:
<source lang=C>
if (<expression>)
    <statement1>
else
    <statement2>
</source>

In the {{code|if}} statement, if the {{code|<expression>}} in parentheses is nonzero (true), control passes to {{code|<statement1>}}. If the {{code|else}} clause is present and the {{code|<expression>}} is zero (false), control will pass to {{code|<statement2>}}. The {{code|else <statement2>}} part is optional and, if absent, a false {{code|<expression>}} will simply result in skipping over the {{code|<statement1>}}. An {{code|else}} always matches the nearest previous unmatched {{code|if}}; braces may be used to override this when necessary, or for clarity.

The {{code|switch}} statement causes control to be transferred to one of several statements depending on the value of an [[Expression (mathematics)|expression]], which must have integral type. The substatement controlled by a switch is typically compound. Any statement within the substatement may be labeled with one or more {{code|case}} labels, which consist of the keyword {{code|case}} followed by a constant expression and then a colon (:). The syntax is as follows:
<source lang=C>
switch (<expression>)
{
    case <label1> :
        <statements 1>
    case <label2> :
        <statements 2>
        break;
    default :
        <statements 3>
}
</source>

No two of the case constants associated with the same switch may have the same value. There may be at most one {{code|default}} label associated with a switch. If none of the case labels are equal to the expression in the parentheses following {{code|switch}}, control passes to the {{code|default}} label or, if there is no {{code|default}} label, execution resumes just beyond the entire construct.

Switches may be nested; a {{code|case}} or {{code|default}} label is associated with the innermost {{code|switch}} that contains it. Switch statements can "fall through", that is, when one case section has completed its execution, statements will continue to be executed downward until a {{code|break;}} statement is encountered. Fall-through is useful in some circumstances, but is usually not desired.
In the preceding example, if {{code|<label2>}} is reached, the statements {{code|<statements 2>}} are executed and nothing more inside the braces. However, if {{code|<label1>}} is reached, both {{code|<statements 1>}} and {{code|<statements 2>}} are executed since there is no {{code|break}} to separate the two case statements.

It is possible, although unusual, to insert the {{code|switch}} labels into the sub-blocks of other control structures. Examples of this include [[Duff's device]] and Simon Tatham's implementation of [[Coroutine|coroutine]]s in Putty.<ref>{{cite web | first=Simon | last=Tatham |  date=2000 | url=https://www.chiark.greenend.org.uk/~sgtatham/coroutines.html | title = Coroutines in C| access-date=2017-04-30}}</ref>

===Iteration statements===
C has three forms of [[Iteration|iteration]] statement:
<source lang=C>
do
    <statement>
while ( <expression> ) ;

while ( <expression> )
    <statement>

for ( <expression> ; <expression> ; <expression> )
    <statement>
</source>

In the [[While loop|{{code|while}}]] and {{code|do}} statements, the sub-statement is executed repeatedly so long as the value of the {{code|expression}} remains non-zero (equivalent to true). With {{code|while}}, the test, including all side effects from {{code|<expression>}}, occurs before each iteration (execution of {{code|<statement>}}); with {{code|do}}, the test occurs after each iteration. Thus, a {{code|do}} statement always executes its sub-statement at least once, whereas {{code|while}} may not execute the sub-statement at all.

The statement:
<source lang=C>
for (e1; e2; e3)
    s;
</source>
is equivalent to:
<source lang=C>
e1;
while (e2)
{
    s;
cont:
    e3;
}
</source>
except for the behaviour of a {{code|continue;}} statement (which in the {{code|for}} loop jumps to {{code|e3}} instead of {{code|e2}}). If {{code|e2}} is blank, it would have to be replaced with a {{code|1}}.

Any of the three expressions in the {{code|for}} loop may be omitted. A missing second expression makes the {{code|while}} test always non-zero, creating a potentially infinite loop.

Since [[C99]], the first expression may take the form of a declaration, typically including an initializer, such as:
<source lang=C>
for (int i = 0; i < limit; ++i) {
    // ...
}
</source>

The declaration's scope is limited to the extent of the {{code|for}} loop.

===Jump statements===
Jump statements transfer control unconditionally. There are four types of [[Branch (computer science)|jump statements]] in C: {{code|goto}}, {{code|continue}}, {{code|break}}, and [[Return statement|{{code|return}}]].

The {{code|goto}} statement looks like this:
<source lang=C>
goto <identifier> ;
</source>

The [[Identifier|identifier]] must be a label (followed by a colon) located in the current function. Control transfers to the labeled statement.

A {{code|continue}} statement may appear only within an [[C syntax#Iteration statements|iteration statement]] and causes control to pass to the loop-continuation portion of the innermost enclosing iteration statement. That is, within each of the statements

<source lang=C>
while (expression)
{
    /* ... */
    cont: ;
}

do
{
    /* ... */
    cont: ;
} while (expression);

for (expr1; expr2; expr3) {
     /* ... */
     cont: ;
}
</source>

a {{code|continue}} not contained within a nested iteration statement is the same as {{code|goto cont}}.

The {{code|break}} statement is used to end a {{code|for}} loop, {{code|while}} loop, {{code|do}} loop, or {{code|switch}} statement. Control passes to the statement following the terminated statement.

A function returns to its caller by the {{code|return}} statement. When {{code|return}} is followed by an expression, the value is returned to the caller as the value of the function. Encountering the end of the function is equivalent to a {{code|return}} with no expression. In that case, if the function is declared as returning a value and the caller tries to use the returned value, the result is undefined.

====Storing the address of a label====
[[Software:GNU Compiler Collection|GCC]] extends the C language with a unary {{code|&&}} operator that returns the address of a label. This address can be stored in a {{code|void*}} variable type and may be used later in a {{code|goto}} instruction. For example, the following prints {{code|"hi "}} in an infinite loop:

<source lang=C>
    void *ptr = &&J1;

J1: printf("hi ");
    goto *ptr;
</source>

This feature can be used to implement a jump table.

==Functions==

===Syntax===
A C function definition consists of a [[Return type|return type]] ({{code|void}} if no value is returned), a unique name, a list of parameters in parentheses, and various statements:
<source lang=C>
<return-type> functionName( <parameter-list> )
{
    <statements>
    return <expression of type return-type>;
}
</source>

A function with non-{{code|void}} return type should include at least one {{code|return}} statement. The parameters are given by the {{code|<parameter-list>}}, a comma-separated list of parameter declarations, each item in the list being a data type followed by an identifier: {{code|<data-type> <variable-identifier>, <data-type> <variable-identifier>, ...}}.

The return type cannot be an array type or function type.
<source lang=C>
int f()[3];    // Error: function returning an array
int (*g())[3]; // OK: function returning a pointer to an array.

void h()();    // Error: function returning a function
void (*k())(); // OK: function returning a function pointer
</source>

If there are no parameters, the {{code|<parameter-list>}} may be left empty or optionally be specified with the single word {{code|void}}.

It is possible to define a function as taking a variable number of parameters by providing the {{code|...}} keyword as the last parameter instead of a data type ad variable identifier. A commonly used function that does this is the standard library function {{code|printf}}, which has the declaration:
<source lang=C>
int printf (const char*, ...);
</source>

Manipulation of these parameters can be done by using the routines in the standard library header [[Stdarg.h|{{code|<stdarg.h>}}]].

====Function Pointers====
A pointer to a function can be declared as follows:
<source lang=C>
<return-type> (*<function-name>)(<parameter-list>);
</source>

The following program shows use of a [[Function pointer|function pointer]] for selecting between addition and subtraction:
<source lang=C>
#include <stdio.h>

int (*operation)(int x, int y);

int add(int x, int y)
{
    return x + y;
}

int subtract(int x, int y)
{
    return x - y;
}

int main(int argc, char* args[])
{
   int  foo = 1, bar = 1;

   operation = add;
   printf("%d + %d = %d\n", foo, bar, operation(foo, bar));
   operation = subtract;
   printf("%d - %d = %d\n", foo, bar, operation(foo, bar));
   return 0;
}
</source>

===Global structure===
After preprocessing, at the highest level a [[C (programming language)|C]] [[Computer program|program]] consists of a sequence of declarations at file scope. These may be partitioned into several separate source files, which may be compiled separately; the resulting object modules are then [[Linker (computing)|linked]] along with implementation-provided run-time support modules to produce an executable image.

The declarations introduce functions, variables and [[Data type|types]]. C functions are akin to the subroutines of [[Fortran]] or the procedures of [[Pascal (programming language)|Pascal]].

A ''definition'' is a special type of declaration. A variable definition sets aside storage and possibly initializes it, a function definition provides its body.

An implementation of C providing all of the standard library functions is called a ''hosted implementation''. Programs written for hosted implementations are required to define a special function called [[Entry point|{{code|main}}]], which is the first function called when a program begins executing.

Hosted implementations start program execution by invoking the {{code|main}} function, which must be defined following one of these prototypes:
<source lang=C>
int main() {...}
int main(void) {...}
int main(int argc, char *argv[]) {...}
int main(int argc, char **argv) {...}
</source>

The first two definitions are equivalent (and both are compatible with C++). It is probably up to individual preference which one is used (the current C standard contains two examples of {{code|main()}} and two of {{code|main(void)}}, but the draft C++ standard uses {{code|main()}}). The return value of {{code|main}} (which should be {{code|int}}) serves as ''termination status'' returned to the host environment.

The C standard defines return values {{code|0}} and {{code|EXIT_SUCCESS}} as indicating success and {{code|EXIT_FAILURE}} as indicating failure. ({{code|EXIT_SUCCESS}} and {{code|EXIT_FAILURE}} are defined in {{code|<stdlib.h>}}). Other return values have implementation-defined meanings; for example, under [[Software:Linux|Linux]] a program killed by a signal yields a return code of the numerical value of the signal plus 128.

A minimal correct C program consists of an empty {{code|main}} routine, taking no arguments and doing nothing:
<source lang=C>
int main(void){}
</source>

Because no <code>return</code> statement is present, <code>main</code> returns 0 on exit.<ref name="bk21st" /> (This is a special-case feature introduced in [[C99]] that applies only to <code>main</code>.)

The {{code|main}} function will usually call other functions to help it perform its job.

Some implementations are not hosted, usually because they are not intended to be used with an [[Operating system|operating system]]. Such implementations are called ''free-standing'' in the C standard. A free-standing implementation is free to specify how it handles program startup; in particular it need not require a program to define a {{code|main}} function.

Functions may be written by the programmer or provided by existing libraries. Interfaces for the latter are usually declared by including header files—with the {{code|#include}} preprocessing directive—and the library objects are linked into the final executable image. Certain library functions, such as [[Printf|{{code|printf}}]], are defined by the C standard; these are referred to as the standard library functions.

A function may return a value to caller (usually another C function, or the hosting environment for the function {{code|main}}). The {{code|printf}} function mentioned above returns how many characters were printed, but this value is often ignored.

===Argument passing===
In C, arguments are passed to functions by value while other languages may pass variables by reference.
This means that the receiving function gets copies of the values and has no direct way of altering the original variables.
For a function to alter a variable passed from another function, the caller must pass its ''address'' (a ''pointer'' to it), which can then be dereferenced in the receiving function. See [[C syntax#Pointers|Pointers]] for more information.

<source lang=C>
void incInt(int *y)
{
    (*y)++;  // Increase the value of 'x', in 'main' below, by one
}

int main(void)
{
    int x = 0;
    incInt(&x);  // pass a reference to the var 'x'
    return 0;
}
</source>

The function [[Software:Scanf|scanf]] works the same way:
<source lang=C>
int x;
scanf("%d", &x);
</source>

In order to pass an editable pointer to a function (such as for the purpose of returning an allocated array to the calling code) you have to pass a pointer to ''that'' pointer: its address.

<source lang=C>
#include <stdio.h>
#include <stdlib.h>

void allocate_array(int ** const a_p, const int A) {
/* 
 allocate array of A ints
 assigning to *a_p alters the 'a' in main()
*/
    *a_p = malloc(sizeof(int) * A); 
}

int main(void) {
    int * a; /* create a pointer to one or more ints, this will be the array */

 /* pass the address of 'a' */
    allocate_array(&a, 42);

/* 'a' is now an array of length 42 and can be manipulated and freed here */

    free(a);
    return 0;
}
</source>

The parameter {{code|int **a_p}} is a pointer to a pointer to an {{code|int}}, which is the address of the pointer {{code|p}} defined in the ''main'' function in this case.

====Array parameters====
Function parameters of array type may at first glance appear to be an exception to C's pass-by-value rule. The following program will print 2, not 1:
<source lang=C>
#include <stdio.h>

void setArray(int array[], int index, int value)
{
    array[index] = value;
}

int main(void)
{
    int a[1] = {1};
    setArray(a, 0, 2);
    printf ("a[0]=%d\n", a[0]);
    return 0;
}
</source>

However, there is a different reason for this behavior. In fact, a function parameter declared with an array type is treated like one declared to be a pointer. That is, the preceding declaration of {{code|setArray}} is equivalent to the following:
<source lang=C>
void setArray(int *array, int index, int value)
</source>

At the same time, C rules for the use of arrays in expressions cause the value of {{code|a}} in the call to {{code|setArray}} to be converted to a pointer to the first element of array {{code|a}}. Thus, in fact this is still an example of pass-by-value, with the caveat that it is the address of the first element of the array being passed by value, not the contents of the array.

Since C99, the programmer can specify that a function takes an array of a certain size by using the keyword {{code|static}}. In <code>void setArray(int array[static 4], int index, int value)</code> the first parameter must be a pointer to the first element of an array of length at least 4. It is also possible to add qualifiers (<code>const</code>, <code>volatile</code> and <code>restrict</code>) to the pointer type that the array is converted to by putting them between the brackets.

==Miscellaneous==

===Reserved keywords===
The following words are [[Reserved word|reserved]], and may not be used as identifiers:

{{col-begin}}
{{col-break|width=20%}}
:{{mono|_Alignas}}
:{{mono|_Alignof}}
:{{mono|_Atomic}}
:{{mono|auto}}
:{{mono|_Bool}}
:{{mono|break}}
:{{mono|case}}
:{{mono|char}}
:{{mono|_Complex}}
:{{mono|const}}
:{{mono|continue}}
:{{mono|default}}
:{{mono|do}}
{{col-break|width=20%}}
:{{mono|double}}
:{{mono|else}}
:{{mono|enum}}
:{{mono|extern}}
:{{mono|float}}
:{{mono|for}}
:{{mono|_Generic}}
:{{mono|goto}}
:{{mono|if}}
:{{mono|_Imaginary}}
:{{mono|inline}}
{{col-break|width=20%}}
:{{mono|int}}
:{{mono|long}}
:{{mono|_Noreturn}}
:{{mono|register}}
:{{mono|restrict}}
:{{mono|return}}
:{{mono|short}}
:{{mono|signed}}
:{{mono|sizeof}}
:{{mono|static}}
:{{mono|struct}}
{{col-break}}
:{{mono|switch}}
:{{mono|_Thread_local}}
:{{mono|typedef}}
:{{mono|union}}
:{{mono|unsigned}}
:{{mono|void}}
:{{mono|volatile}}
:{{mono|while}}
{{col-end}}

Implementations may reserve other keywords, such as {{code|asm}}, although implementations typically provide non-standard keywords that begin with one or two underscores.

===Case sensitivity===
C identifiers are case sensitive (e.g., {{code|foo}}, {{code|FOO}}, and {{code|Foo}} are the names of different objects). Some linkers may map external identifiers to a single case, although this is uncommon in most modern linkers.

===Comments===
Text starting with the [[Lexical analysis#Token|token]] {{code|/*}} is treated as a [[Comment (computer programming)|comment]] and ignored. The comment ends at the next {{code|*/}}; it can occur within expressions, and can span multiple lines. Accidental omission of the comment terminator is problematic in that the next comment's properly constructed comment terminator will be used to terminate the initial comment, and all code in between the comments will be considered as a comment. C-style comments do not nest; that is, accidentally placing a comment within a comment has unintended results:
<source lang=C line="GESHI_FANCY_LINE_NUMBERS">
/*
This line will be ignored.
/*
A compiler warning may be produced here. These lines will also be ignored.
The comment opening token above did not start a new comment,
and the comment closing token below will close the comment begun on line 1.
*/
This line and the line below it will not be ignored. Both will likely produce compile errors.
*/
</source>

[[C++]] style line comments start with {{code|//}} and extend to the end of the line. This style of comment originated in [[BCPL]] and became valid C syntax in [[C99]]; it is not available in the original K&R C nor in [[ANSI C]]:
<source lang=C>
// this line will be ignored by the compiler

/* these lines
   will be ignored
   by the compiler */

x = *p/*q;  /* this comment starts after the 'p' */
</source>

===Command-line arguments===
The [[Parameter|parameter]]s given on a command line are passed to a C program with two predefined variables - the count of the command-line arguments in {{code|argc}} and the individual [[Parameter|arguments]] as character strings in the pointer array {{code|argv}}. So the command:

 myFilt p1 p2 p3

results in something like:
{|class="wikitable" style="font-family: monospace,monospace;"
|-
|m||y||F||i||l||t||style="background:#CCC;"|\0||p||1||style="background:#CCC;"|\0||p||2||style="background:#CCC;"|\0||p||3||style="background:#CCC;"|\0
|-
|colspan="7" align="center"|argv[0]||colspan="3" align="center"|argv[1]||colspan="3" align="center"|argv[2]||colspan="3" align="center"|argv[3]
|}

While individual strings are arrays of contiguous characters, there is no guarantee that the strings are stored as a contiguous group.

The name of the program, {{code|argv[0]}}, may be useful when printing diagnostic messages or for making one binary serve multiple purposes. The individual values of the parameters may be accessed with {{code|argv[1]}}, {{code|argv[2]}}, and {{code|argv[3]}}, as shown in the following program:

<source lang=C>
#include <stdio.h>

int main(int argc, char *argv[])
{
    printf("argc\t= %d\n", argc);
    for (int i = 0; i < argc; i++)
        printf("argv[%i]\t= %s\n", i, argv[i]);
}
</source>

===Evaluation order===
In any reasonably complex expression, there arises a choice as to the order in which to evaluate the parts of the expression: {{C-lang|(1+1)+(3+3)}} may be evaluated in the order {{C-lang|(1+1)+(3+3)}}, {{C-lang|(2)+(3+3)}}, {{C-lang|(2)+(6)}}, {{C-lang|(8)}}, or in the order {{C-lang|(1+1)+(3+3)}}, {{C-lang|(1+1)+(6)}}, {{C-lang|(2)+(6)}}, {{C-lang|(8)}}. Formally, a conforming C compiler may evaluate expressions in ''any'' order between ''[[Sequence point|sequence point]]s'' (this allows the compiler to do some optimization). Sequence points are defined by:
* ''Statement ends'' at semicolons.
* The ''sequencing operator'': a comma. However, commas that delimit function arguments are not sequence points.
* The ''short-circuit operators'': logical ''and'' ({{code|&&}}, which can be read ''and then'') and logical ''or'' (<code>||</code>, which can be read ''or else'').
* The ''[[?:|ternary operator]]'' ({{code|?:}}): This operator evaluates its first sub-expression first, and then its second or third (never both of them) based on the value of the first.
* Entry to and exit from a ''function call'' (but not between evaluations of the arguments).

Expressions before a sequence point are always evaluated before those after a sequence point. In the case of short-circuit evaluation, the second expression may not be evaluated depending on the result of the first expression. For example, in the expression {{C-lang|(a() {{!}}{{!}} b())}}, if the first argument evaluates to nonzero (true), the result of the entire expression cannot be anything else than true, so {{code|b()}} is not evaluated. Similarly, in the expression {{C-lang|(a() && b())}}, if the first argument evaluates to zero (false), the result of the entire expression cannot be anything else than false, so {{code|b()}} is not evaluated.

The arguments to a function call may be evaluated in any order, as long as they are all evaluated by the time the function is entered. The following expression, for example, has undefined behavior:
<source lang=C>
 printf("%s %s\n", argv[i = 0], argv[++i]);
</source>

===Undefined behavior===
{{main|Undefined behavior}}
An aspect of the C standard (not unique to C) is that the behavior of certain code is said to be "undefined". In practice, this means that the program produced from this code can do anything, from working as the programmer intended, to crashing every time it is run.

For example, the following code produces undefined behavior, because the variable ''b'' is modified more than once with no intervening sequence point:

<source lang=C>
#include <stdio.h>

int main(void)
{
    int b = 1;
    int a = b++ + b++;
    printf("%d\n", a);
}
</source>

Because there is no sequence point between the modifications of ''b'' in "''b''++ + ''b''++", it is possible to perform the evaluation steps in more than one order, resulting in an ambiguous statement. This can be fixed by rewriting the code to insert a sequence point in order to enforce an unambiguous behavior, for example:
<source lang=C>
a = b++;
a += b++;
</source>

==See also==
*[[Blocks (C language extension)]]
*[[C (programming language)|C programming language]]
*C variable types and declarations
*[[Operators in C and C++]]
*[[C standard library]]
*[[List of C-family programming languages]] (C-influenced languages)

==Notes==
{{reflist|group=note}}

==References==
{{Reflist | refs=
<ref name="bk21st">{{cite book | last = Klemens | first = Ben |  title = 21st Century C | publisher = O'Reilly Media | date = 2012 | isbn = 978-1449327149 }}</ref>
}}

;General
{{Refbegin}}
*{{cite book |last=Kernighan |first=Brian W. |author2=Ritchie, Dennis M. |author-link2=Dennis Ritchie  |title=The C Programming Language |url=https://archive.org/details/cprogramminglang00bria |url-access=registration |edition=2nd |year=1988 |publisher=Prentice Hall PTR |location=Upper Saddle River, New Jersey |isbn=0-13-110370-9}}
* American National Standard for Information Systems - Programming Language - C - ANSI X3.159-1989
*{{cite web|url=https://www.iso.org/standard/74528.html|title=ISO/IEC 9899:2018 - Information technology -- Programming languages -- C|website=International Organization for Standardization}}
*{{cite web|url=https://www.iso.org/iso/iso_catalogue/catalogue_ics/catalogue_detail_ics.htm?csnumber=29237 |title=ISO/IEC 9899:1999 - Programming languages - C |publisher=Iso.org |date=2011-12-08 |access-date=2014-04-08}}
{{Refend}}

==External links==
*[http://www.cs.man.ac.uk/~pjj/bnf/c_syntax.bnf ''The syntax of C in Backus-Naur form'']
*[https://users.cs.cf.ac.uk/Dave.Marshall/C/CE.html Programming in C]
*[http://c-faq.com/ ''The comp.lang.c Frequently Asked Questions Page'']

{{CProLang}}

{{DEFAULTSORT:C Syntax}}
[[Category:C (programming language)]]
[[Category:Source code]]
[[Category:Programming language syntax]]

{{Sourceattribution|C syntax}}