C1X
   HOME

TheInfoList



OR:

C11 (previously C1X, formally ISO/IEC 9899:2011) is a past
standard Standard may refer to: Symbols * Colours, standards and guidons, kinds of military signs * Standard (emblem), a type of a large symbol or emblem used for identification Norms, conventions or requirements * Standard (metrology), an object ...
for the C programming language. It replaced
C99 C99 (previously C9X, formally ISO/IEC 9899:1999) is a past version of the C programming language open standard. It extends the previous version ( C90) with new features for the language and the standard library, and helps implementations mak ...
(standard ISO/IEC 9899:1999) and has been superseded by C17 (standard ISO/IEC 9899:2018). C11 mainly standardizes features already supported by common contemporary compilers, and includes a detailed memory model to better support multiple threads of execution. Due to delayed availability of conforming C99 implementations, C11 makes certain features optional, to make it easier to comply with the core language standard. The final draft, N1570, was published in April 2011. The new standard passed its final draft review on October 10, 2011 and was officially ratified by ISO and published as ISO/IEC 9899:2011 on December 8, 2011, with no comments requiring resolution by participating national bodies. A standard macro __STDC_VERSION__ is defined with value 201112L to indicate that C11 support is available.


Changes from C99

The standard includes several changes to the
C99 C99 (previously C9X, formally ISO/IEC 9899:1999) is a past version of the C programming language open standard. It extends the previous version ( C90) with new features for the language and the standard library, and helps implementations mak ...
language and library specifications, such as *
Alignment Alignment may refer to: Archaeology * Alignment (archaeology), a co-linear arrangement of features or structures with external landmarks * Stone alignment, a linear arrangement of upright, parallel megalithic standing stones Biology * Struc ...
specification (_Alignas specifier, _Alignof operator, aligned_alloc function, <stdalign.h> header) * The _Noreturn function specifier and the <stdnoreturn.h> header * Type-generic expressions using the _Generic keyword. For example, the following macro cbrt(x) translates to cbrtl(x), cbrt(x) or cbrtf(x) depending on the type of x:
#define cbrt(x) _Generic((x), long double: cbrtl, \ default: cbrt, \ float: cbrtf)(x)
* Multi-threading support (_Thread_local storage-class specifier, <threads.h> header including thread creation/management functions,
mutex In computer science, a lock or mutex (from mutual exclusion) is a synchronization primitive that prevents state from being modified or accessed by multiple threads of execution at once. Locks enforce mutual exclusion concurrency control policies, ...
,
condition variable Condition or conditions may refer to: In philosophy and logic * Material conditional The material conditional (also known as material implication) is a binary operation commonly used in logic. When the conditional symbol \to is interprete ...
and thread-specific storage functionality, as well as <stdatomic.h> for atomic operations supporting the C11 memory model). * Improved
Unicode Unicode or ''The Unicode Standard'' or TUS is a character encoding standard maintained by the Unicode Consortium designed to support the use of text in all of the world's writing systems that can be digitized. Version 16.0 defines 154,998 Char ...
support based on the C Unicode Technical Report ISO/IEC TR 19769:2004 (char16_t and char32_t types for storing
UTF-16 UTF-16 (16-bit Unicode Transformation Format) is a character encoding that supports all 1,112,064 valid code points of Unicode. The encoding is variable-length as code points are encoded with one or two ''code units''. UTF-16 arose from an earli ...
/
UTF-32 UTF-32 (32- bit Unicode Transformation Format), sometimes called UCS-4, is a fixed-length encoding used to encode Unicode code points that uses exactly 32 bits (four bytes) per code point (but a number of leading bits must be zero as there are far ...
encoded data, including conversion functions in <uchar.h> and the corresponding u and U string literal prefixes, as well as the u8 prefix for
UTF-8 UTF-8 is a character encoding standard used for electronic communication. Defined by the Unicode Standard, the name is derived from ''Unicode Transformation Format 8-bit''. Almost every webpage is transmitted as UTF-8. UTF-8 supports all 1,112,0 ...
encoded literals). * Removal of the gets function (in favor of safer fgets), which was deprecated in the previous C language standard revision, ISO/IEC 9899:1999/Cor.3:2007(E). * Bounds-checking interfaces (Annex K). * Analyzability features (Annex L). * More macros for querying the characteristics of floating-point types, concerning subnormal floating-point numbers and the number of decimal digits the type is able to store. * Anonymous ''structures'' and ''unions'', useful when unions and structures are nested, e.g. in . * Static assertions, which are evaluated during translation at a later phase than #if and #error, when types are understood by the translator. * An exclusive create-and-open mode ("…x" suffix) for fopen. This behaves like O_CREAT, O_EXCL in
POSIX The Portable Operating System Interface (POSIX; ) is a family of standards specified by the IEEE Computer Society for maintaining compatibility between operating systems. POSIX defines application programming interfaces (APIs), along with comm ...
, which is commonly used for lock files. * The quick_exit function as a third way to terminate a program, intended to do at least minimal deinitialization. * A new timespec_get function and corresponding structure in <time.h> with a degree of
POSIX The Portable Operating System Interface (POSIX; ) is a family of standards specified by the IEEE Computer Society for maintaining compatibility between operating systems. POSIX defines application programming interfaces (APIs), along with comm ...
compatibility. * Macros for the construction of complex values (partly because real + imaginary*I might not yield the expected value if imaginary is infinite or NaN).


Optional features

The new revision allows implementations to not support certain parts of the standard — including some that had been mandatory to support in the 1999 revision. Programs can use predefined macros to determine whether an implementation supports a certain feature or not.


Compiler support

Some features of C11 are supported by the GNU Compiler Collection, GCC starting with version 4.6, Clang starting with version 3.1, IBM XL C starting with version 12.1, and Microsoft Visual C++ starting with VS 2019 (16.8) in September 2020.


Criticism

The optional bounds-checking interfaces (Annex K) remain controversial and have not been widely implemented, and their deprecation or removal from the next standard revision has been proposed. Even Microsoft, a main proponent of this interface, does not conform to the definition. In addition, Annex K does not include the more useful TR24731-2 (dynamic allocation functions), such as and . The few open-source implementations include Open Watcom C/C++'s "Safer C" library and safeclib.


See also

* C++23, C++20, C++17, C++14, C++11, C++03, C++98, versions of the C++ programming language standard * Compatibility of C and C++


References


Further reading


N1570
(working draft of C11 standard); WG14; 2011.
HTML and ASCII versions


(official C11 standard); International Organization for Standardization, ISO; 2011. *
Safe C API—Concise solution of buffer overflow, The OWASP Foundation, OWASP AppSec, Beijing 2011


External links




C1X Charter
- WG14 * sourceforge:projects/safeclib/, Safe C Library of Bounded APIs {{ISO standards C (programming language) Programming language standards IEC standards ISO standards