This article needs additional citations for verification. Please help improve this article by adding citations to reliable sources. Unsourced material may be challenged and removed.Find sources: "ANSI C" – news · newspapers · books · scholar · JSTOR (July 2010) (Learn how and when to remove this message)

ANSI C, also known as C89 and C90 depending on the year of ratification, refers to the family of successive standards published by the American National Standards Institute (ANSI) for the C programming language. Software developers writing in C are encouraged to conform to the standards, as doing so aids portability between compilers.

History and outlook

The first standard for C was published by ANSI. Although this document was subsequently adopted by International Organization for Standardization (ISO) and subsequent revisions published by ISO have been adopted by ANSI, the name ANSI C (rather than ISO C) is still more widely used. While some software developers use the term ISO C, others are standards body–neutral and use Standard C.

C89

In 1983, the American National Standards Institute formed a committee, X3J11, to establish a standard specification of C. After a long and arduous process[citation needed], the 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 C99 but using the same labelling method.

C90

The same standard as C89 was ratified by the International Organization for Standardization as ISO/IEC 9899:1990, with only formatting changes,[1] which is sometimes referred to as C90. Therefore, the terms "C89" and "C90" refer to essentially the same language.

This standard has been withdrawn by both INCITS[2] and ISO/IEC.[3]

AMD1

ISO also published an amendment in 1994, referred to as AMD1, (ISO/IEC 9899/Amd.1:1995) introducing minor changes to the language and the library.[4]

C95

1995 the ISO published an extension, called Amendment 1, for the ANSI-C standard. It full name finally was ISO/IEC 9899/AMD1:1995 or nicknamed C95. Aside to error correction there were further changes to the language capabilities.[5] [6]

Most important additions to C95

Preprocessor Test for C95 compatibility

#if defined(__STDC_VERSION__) && __STDC_VERSION__ >= 199409L
/*
 * C95 compatible source code.
 */
#endif

C99

In March 2000, ANSI adopted the ISO/IEC 9899:1999 standard. This standard is commonly referred to as C99.

This standard has been withdrawn by ISO/IEC in favour of C11,[7] but is still approved by INCITS.[citation needed]

C11

"C11" is the new standard for the C programming language.

Support from major compilers

This section does not cite any sources. Please help improve this section by adding citations to reliable sources. Unsourced material may be challenged and removed. (June 2011) (Learn how and when to remove this message)

ANSI C is now supported by almost all the widely used compilers. Most of the C code being written nowadays is based on ANSI C. Any program 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 detectability

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

 #if __STDC__
 extern int getopt(int, char * const *, const char *);
 #else
 extern int getopt();
 #endif

It's better to use "#if __STDC__" as above rather than "#ifdef __STDC__" because some implementation may set __STDC__ to zero to indicate non-ANSI compliance. "#if" will treat any identifiers that couldn't be replaced by a macro as zero (0). Thus even if the macro "__STDC__" is not defined to signify non-ANSI compliance, "#if" will work as shown.

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

Compilers supporting ANSI C

References

  1. ^ "Standards - Using the GNU Compiler Collection (GCC)". Retrieved 2012-06-24.
  2. ^ http://www.techstreet.com/cgi-bin/detail?doc_no=incits_iso_iec%7C9899;product_id=232462
  3. ^ "ISO/IEC 9899:1990 - Programming Languages -- C". Retrieved 2012-06-24.
  4. ^ "A brief description of Normative Addendum 1". Retrieved 2013-09-12.
  5. ^ Clive D.W. Feather. "A brief description of Normative Addendum 1". Retrieved 2010-09-12.
  6. ^ "ISO/IEC 9899:1990/Amd 1:1995". International Organization for Standardization. Retrieved 2013-03-22.
  7. ^ "ISO/IEC 9899:1999 - Programming Languages -- C". Retrieved 2012-06-24.