|
ANSI C
ANSI C, ISO C, and Standard C are successive standards for the C programming language published by the American National Standards Institute (ANSI) and ISO/IEC JTC 1/SC 22/WG 14 of the International Organization for Standardization (ISO) and the International Electrotechnical Commission (IEC). Historically, the names referred specifically to the original and best-supported version of the standard (known as C89 or C90). Software developers writing in C are encouraged to conform to the standards, as doing so helps portability between compilers. History and outlookThe first standard for C was published by ANSI. Although this document was subsequently adopted by ISO/IEC and subsequent revisions published by ISO/IEC have been adopted by ANSI, "ANSI C" is still used to refer to the standard.[1] While some software developers use the term ISO C, others are standards-body neutral and use Standard C. Informal specification: K&R C (C78)Informal specification in 1978 (Brian Kernighan and Dennis Ritchie book The C Programming Language). Standardizing CIn 1983, the American National Standards Institute formed a committee, X3J11, to establish a standard specification of C. In 1985, the first Standard Draft was released, sometimes referred to as C85. In 1986, another Draft Standard was released, sometimes referred to as C86. The prerelease Standard C was published in 1988, and sometimes referred to as C88.[2] C89The ANSI standard was completed in 1989 and ratified as ANSI X3.159-1989 "Programming Language C." This version of the language is often referred to as "ANSI C". Later on sometimes the label "C89" is used to distinguish it from C90 but using the same labeling method. C90The same standard as C89 was ratified by ISO/IEC as ISO/IEC 9899:1990, with only formatting changes,[3] which is sometimes referred to as C90. Therefore, the terms "C89" and "C90" refer to a language that is virtually identical. This standard has been withdrawn by both ANSI/INCITS[4] and ISO/IEC.[5] C95In 1995, the ISO/IEC published an extension, called Amendment 1, for the C standard. Its full name finally was ISO/IEC 9899:1990/AMD1:1995 or nicknamed C95. Aside from error correction there were further changes to the language capabilities,[6][7] such as:
In addition to the amendment, two technical corrigenda were published by ISO for C90: Preprocessor test for C95 compatibility#if defined(__STDC_VERSION__) && __STDC_VERSION__ >= 199409L
/* C95 compatible source code. */
#elif defined(__STDC__)
/* C89 compatible source code. */
#endif
C99In March 2000, ANSI adopted the ISO/IEC 9899:1999 standard.[10] This standard is commonly referred to as C99. Some notable additions to the previous standard include:
Three technical corrigenda were published by ISO for C99:
This standard has been withdrawn by both ANSI/INCITS[11] and ISO/IEC[12] in favour of C11. C11C11 was officially ratified and published on December 8, 2011. Notable features include improved Unicode support, type-generic expressions using the new One technical corrigendum has been published by ISO for C11:
C17C17 was published in June 2018.[14] Rather than introducing new language features, it only addresses defects in C11.[15] C23C23 was published in October 2024, and is the current standard for the C programming language.[16] Other related ISO publicationsAs part of the standardization process, ISO/IEC also publishes technical reports and specifications related to the C language:
More technical specifications are in development and pending approval, including the fifth and final part of TS 18661, a software transactional memory specification, and parallel library extensions.[28] Support from major compilersANSI C is now supported by almost all the widely used compilers. GCC and Clang are two major C compilers popular today, both based on the C11 with updates including changes from later specifications such as C17.[29][30] Any source code written only in standard C and without any hardware dependent assumptions is virtually guaranteed to compile correctly on any platform with a conforming C implementation. Without such precautions, most programs may compile only on a certain platform or with a particular compiler, due, for example, to the use of non-standard libraries, such as GUI libraries, or to the reliance on compiler- or platform-specific attributes such as the exact size of certain data types and byte endianness. Compliance detectabilityTo mitigate the differences between K&R C and the ANSI C standard, the #if defined(__STDC__) && __STDC__
extern int getopt(int, char * const *, const char *);
#else
extern int getopt();
#endif
In the above example, a prototype is used in a function declaration for ANSI compliant implementations, while an obsolescent non-prototype declaration is used otherwise. Those are still ANSI-compliant as of C99. Note how this code checks both definition and evaluation: this is because some implementations may set Compiler supportList of compilers supporting ANSI C:
See also
References
Further reading
External links
|
|||||||||||||||||||||||||||||
