ANSI C,ISO C,andStandard Care successive standards for theC programming languagepublished by theAmerican National Standards Institute(ANSI) andISO/IEC JTC 1/SC 22/WG 14 of theInternational Organization for Standardization(ISO) and theInternational Electrotechnical Commission(IEC). Historically, the names referred specifically to the original and best-supported version of the standard (known asC89orC90). Software developers writing in C are encouraged to conform to the standards, as doing so helpsportabilitybetween compilers.

History and outlook

edit

The 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)

edit

Informalspecificationin 1978 (Brian KernighanandDennis RitchiebookThe C Programming Language).

Standardizing C

edit

In 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 asC85.In 1986, another Draft Standard was released, sometimes referred to asC86.The prerelease Standard C was published in 1988, and sometimes referred to asC88.[2]

The 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.

The 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]

In 1995, theISO/IECpublished an extension, called Amendment 1, for the C standard. Its full name finally wasISO/IEC 9899:1990/AMD1:1995or nicknamedC95.Aside from error correction there were further changes to the language capabilities,[6][7]such as:

  • Improvedmulti-byteandwide charactersupport in the standard library, introducing<wchar.h>and<wctype.h>as well asmulti-byteI/O
  • Addition ofdigraphsto the language
  • Specification of standard macros for the alternative specification of operators, e.g.andfor&&
  • Specification of the standard macro__STDC_VERSION__

In addition to the amendment, two technical corrigenda were published by ISO for C90:

  • ISO/IEC 9899:1990/Cor 1:1994 TCOR1 in 1994[8]
  • ISO/IEC 9899:1990/Cor 2:1996 in 1996[9]

Preprocessor test for C95 compatibility

edit
#if defined(__STDC_VERSION__) && __STDC_VERSION__ >= 199409L

/* C95 compatible source code. */
#elif defined(__STDC__)
/* C89 compatible source code. */
#endif

In 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:

  • ISO/IEC 9899:1999/Cor 1:2001(E)
  • ISO/IEC 9899:1999/Cor 2:2004(E)
  • ISO/IEC 9899:1999/Cor 3:2007(E), notable for deprecating the standard library functiongets

This standard has been withdrawn by both ANSI/INCITS[11]and ISO/IEC[12]in favour of C11.

C11 was officially ratified and published on December 8, 2011. Notable features include improvedUnicodesupport, type-generic expressions using the new_Generickeyword, a cross-platformmulti-threadingAPI (threads.h), andatomictypes support in both core language and the library (stdatomic.h).

One technical corrigendum has been published by ISO for C11:

  • ISO/IEC 9899:2011/Cor 1:2012[13]

As of October 2018,"C17" is the currentstandardfor theC programming language.[14]

C17 addresses defects in C11 without introducing new language features.[15]

C23 is the informal name for the next majorC languagestandard revision.[16]

edit

As part of the standardization process, ISO/IEC also publishestechnical reports and specificationsrelated to the C language:

  • ISO/IEC TR 19769:2004,[17]on library extensions to support Unicode transformation formats, integrated into C11
  • ISO/IEC TR 24731-1:2007,[18]on library extensions to support bounds-checked interfaces, integrated into C11
  • ISO/IEC TR 18037:2008,[19]on embedded C extensions
  • ISO/IEC TR 24732:2009,[20]ondecimal floating pointarithmetic, superseded by ISO/IEC TS 18661-2:2015
  • ISO/IEC TR 24747:2009,[21]on special mathematical functions,
  • ISO/IEC TR 24731-2:2010,[22]on library extensions to support dynamic allocation functions
  • ISO/IEC TS 17961:2013,[23]on secure coding in C
  • ISO/IEC TS 18661-1:2014,[24]onIEC 60559:2011-compatible binary floating-point arithmetic
  • ISO/IEC TS 18661-2:2015,[25]on IEC 60559:2011-compatibledecimal floating pointarithmetic
  • ISO/IEC TS 18661-3:2015,[26]on IEC 60559:2011-compatible interchange and extended floating-point types
  • ISO/IEC TS 18661-4:2015,[27]on IEC 60559:2011-compatible supplementary functions

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 compilers

edit

ANSI 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 writtenonlyin standard C and without any hardware dependent assumptions is virtually guaranteed to compile correctly on anyplatformwith 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 asGUIlibraries, or to the reliance on compiler- or platform-specific attributes such as the exact size of certain data types and byteendianness.

Compliance detectability

edit

To mitigate the differences betweenK&R Cand the ANSI C standard, the__STDC__( "standard c" ) macro can be used to split code into ANSI and K&R sections.

#if defined(__STDC__) && __STDC__
externintgetopt(int,char*const*,constchar*);
#else
externintgetopt();
#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__STDC__to zero to indicate non-ANSI compliance.[31]

Compiler support

edit

List of compilers supporting ANSI C:

See also

edit

References

edit
  1. ^Brad Kelechava (2017-09-14)."The Origin of ANSI C and ISO C".Retrieved2018-08-14.
  2. ^Richard Hale Shaw (13 September 1988)."Standard C: The ANSI Draft Grows Up".PC Magazine.Vol. 7, no. 15. pp. 116–117.Retrieved15 November2022.
  3. ^"Standards - Using the GNU Compiler Collection (GCC)".Retrieved2012-06-24.
  4. ^"INCITS/ISO/IEC 9899".www.techstreet.com.Retrieved2018-10-03.
  5. ^"ISO/IEC 9899:1990 - Programming Languages -- C".Retrieved2012-06-24.
  6. ^Clive D.W. Feather (2010-09-12)."A brief description of Normative Addendum 1".
  7. ^"ISO/IEC 9899:1990/Amd 1:1995".International Organization for Standardization. 2013-03-22.
  8. ^"ISO/IEC 9899:1990/Cor 1:1994".ISO.Retrieved2019-01-21.
  9. ^"ISO/IEC 9899:1990/Cor 2:1996".ISO.Retrieved2019-01-21.
  10. ^"ISO/IEC 9899:1999".ISO.Retrieved2019-01-21.
  11. ^"INCITS/ISO/IEC 9899-2012".ANSI.
  12. ^"ISO/IEC 9899:1999 - Programming Languages -- C".Retrieved2012-06-24.
  13. ^"ISO/IEC 9899:2011/Cor 1:2012".International Organization for Standardization.
  14. ^"ISO/IEC 9899:2018 - Information technology -- Programming languages -- C".www.iso.org.
  15. ^"The Standard - C".www.iso-9899.info.
  16. ^"History of C".cppreference.
  17. ^"ISO/IEC TR 19769:2004".International Organization for Standardization.
  18. ^"ISO/IEC TR 24731-1:2007".International Organization for Standardization.
  19. ^"ISO/IEC TR 18037:2008".International Organization for Standardization.
  20. ^"ISO/IEC TR 24732:2009".International Organization for Standardization.
  21. ^"ISO/IEC TR 24747:2009".International Organization for Standardization.
  22. ^"ISO/IEC TR 24731-2:2010".International Organization for Standardization.
  23. ^"ISO/IEC TS 17961:2013".International Organization for Standardization.
  24. ^"ISO/IEC TS 18661-1:2014".International Organization for Standardization.
  25. ^"ISO/IEC TS 18661-2:2015".International Organization for Standardization.
  26. ^"ISO/IEC TS 18661-3:2015".International Organization for Standardization.
  27. ^"ISO/IEC TS 18661-4:2015".International Organization for Standardization.
  28. ^"Experimental C features".cppreference.com.Retrieved16 January2016.
  29. ^"2 Language Standards Supported by GCC - 2.1 C Language".Using the GNU Compiler Collection (GCC).GCC, the GNU Compiler Collection.Retrieved2019-02-05.
  30. ^"Language Compatibility".Clang C Language Family Frontend for LLVM.Retrieved2019-02-05.
  31. ^"Standard predefined macro names".www.ibm.com.Retrieved2019-04-10.
  32. ^"HP C/ANSI C developer's bundle".Retrieved2015-07-12.
  33. ^Support for ISO C11 added to IBM XL C/C++ compilers
  34. ^link to Pelles C pages

Further reading

edit
  • Schreiner, Axel-Tobias (1993).Object Oriented Programming with ANSI-C.Hanser.ISBN3-446-17426-5.
edit