Information technology — Programming languages — C — Technical Corrigendum 1

Technologies de l'information — Langages de programmation — C — Rectificatif technique 1

General Information

Status

Withdrawn

Publication Date

12-Jul-2012

Withdrawal Date

12-Jul-2012

ICS

35.060 - Languages used in information technology

Technical Committee

ISO/IEC JTC 1/SC 22 - Programming languages, their environments and system software interfaces

Drafting Committee

ISO/IEC JTC 1/SC 22/WG 14 - C

Current Stage

9599 - Withdrawal of International Standard

Completion Date

05-Jul-2018

Ref Project

Relations

Revised

ISO/IEC 9899:2018 - Information technology — Programming languages — C

Effective Date

23-Sep-2017

Corrects

ISO/IEC 9899:2011 - Information technology — Programming languages — C

Effective Date

26-Nov-2021

Buy Standard

Standard

ISO/IEC 9899:2011/Cor 1:2012

English language

2 pages

sale 15% off

Preview

sale 15% off

Preview

Standards Content (Sample)

ISO/IEC 9899:2011/Cor 1:2012

INTERNATIONAL STANDARD ISO/IEC 9899:2011
TECHNICAL CORRIGENDUM 1
Published 2012-07-15
INTERNATIONAL ORGANIZATION FOR STANDARDIZATION  МЕЖДУНАРОДНАЯ ОРГАНИЗАЦИЯ ПО СТАНДАРТИЗАЦИИ  ORGANISATION INTERNATIONALE DE NORMALISATION
INTERNATIONAL ELECTROTECHNICAL COMMISSION  МЕЖДУНАРОДНАЯ ЭЛЕКТРОТЕХНИЧЕСКАЯ КОМИССИЯ  COMMISSION ÉLECTROTECHNIQUE INTERNATIONALE

Information technology — Programming languages — C
TECHNICAL CORRIGENDUM 1
Technologies de l'information — Langages de programmation — C
RECTIFICATIF TECHNIQUE 1
Technical Corrigendum 1 to ISO/IEC 9899:2011 was prepared by Joint Technical Committee ISO/IEC JTC 1,
Information technology, Subcommittee SC 22, Programming languages, their environments and system
software interfaces.

Page 176,
...

Questions, Comments and Discussion

Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.

This May Also Interest You

ISO

ISO/IEC 8652:2023(Main)

Information technology — Programming languages — Ada

oSIST ISO/IEC DIS 8652:2021

This document specifies the form and meaning of programs written in Ada. Its purpose is to promote the portability of Ada programs to a variety of computing systems. This document specifies: — The form of a program written in Ada; — The effect of translating and executing such a program; — The manner in which program units can be combined to form Ada programs; — The language-defined library units that a conforming implementation is required to supply; — The permissible variations in conformance to the rules of this document, and the manner in which they are to be documented; — Those violations of the requirements of this document that a conforming implementation is required to detect, and the effect of attempting to translate or execute a program containing such violations; — Those violations of the requirements of this document that a conforming implementation is not required to detect. This document does not specify: — The means whereby a program written in Ada is transformed into object code executable by a processor; — The means whereby translation or execution of programs is invoked and the executing units are controlled; — The size or speed of the object code, or the relative execution speed of different language constructs; — The form or contents of any listings produced by implementations; in particular, the form or contents of error or warning messages; — The effect of unspecified execution; — The size of a program or program unit that will exceed the capacity of a particular conforming implementation.

Standard
1048 pages
English language
sale 15% off

ISO

ISO/IEC 1539-1:2018/Cor 2:2023(Corrigendum)

Information technology — Programming languages — Fortran — Part 1: Base language — Technical Corrigendum 2

Standard
6 pages
English language
sale 15% off
Standard
6 pages
English language
sale 15% off

ISO

ISO/IEC 1989:2023(Main)

Information technology — Programming languages, their environments and system software interfaces — Programming language COBOL

This document specifies the syntax and semantics of COBOL. Its purpose is to promote a high degree of machine independence to permit the use of COBOL on a variety of data processing systems. This document specifies: The form of a compilation group written in COBOL. The effect of compiling a compilation group. The effect of executing run units. The elements of the language for which a conforming implementation is required to supply a definition. The elements of the language for which meaning is explicitly undefined. The elements of the language that are dependent on the capabilities of the processor. This document does not specify: The means whereby a compilation group written in COBOL is compiled into code executable by a processor. The time at which method, function, or program runtime modules are linked or bound to an activating statement, except that runtime binding occurs of necessity when the identification of the appropriate program or method is not known at compile time. The time at which parameterized classes and interfaces are expanded. The mechanism by which locales are defined and made available on a processor. The form or content of error, flagging, or warning messages. The form and content of listings produced during compilation, if any. The form of documentation produced by an implementor of products conforming to this document. The sharing of objects and resources other than files among run units.

Standard
1229 pages
English language
sale 15% off

ISO

ISO/IEC TS 23619:2021(Main)

Information technology — C++ extensions for reflection

This document describes extensions to the C++ Programming Language (Clause 2) that enable operations on source code. These extensions include new syntactic forms and modifications to existing language semantics, as well as changes and additions to the existing library facilities. Instructions to modify or add paragraphs are written as explicit instructions. Modifications made directly to existing text from ISO/IEC 14882:2020 use underlining to represent added text and strikethrough to represent deleted text.

Technical specification
46 pages
English language
sale 15% off
Draft
46 pages
English language
sale 15% off

ISO

ISO/IEC 1539-1:2018/Cor 1:2021(Corrigendum)

Information technology — Programming languages — Fortran — Part 1: Base language — Technical Corrigendum 1

Standard
6 pages
English language
sale 15% off

ISO

ISO/IEC 14882:2020(Main)

Programming languages — C++

This document specifies requirements for implementations of the C++ programming language. The first such requirement is that they implement the language, so this document also defines C++. Other requirements and relaxations of the first requirement appear at various places within this document. C++ is a general purpose programming language based on the C programming language as described in ISO/IEC 9899:2018 Programming languages — C (hereinafter referred to as the C standard). C++ provides many facilities beyond those provided by C, including additional data types, classes, templates, exceptions, namespaces, operator overloading, function name overloading, references, free store management operators, and additional library facilities.

Standard
1853 pages
English language
sale 15% off

ISO

ISO/IEC TR 24772-3:2020(Main)

Programming languages — Guidance to avoiding vulnerabilities in programming languages — Part 3: C

This document specifies software programming language vulnerabilities to be avoided in the development of systems where assured behaviour is required for security, safety, mission-critical and business-critical software. In general, this guidance is applicable to the software developed, reviewed, or maintained for any application. This document describes the way that the vulnerabilities listed in ISO/IEC TR 24772-1 are manifested or avoided in the C language.

Technical report
42 pages
English language
sale 15% off
Technical report
42 pages
English language
sale 15% off

ISO

ISO/IEC TR 24772-2:2020(Main)

Programming languages — Guidance to avoiding vulnerabilities in programming languages — Part 2: Ada

This document specifies software programming language vulnerabilities to be avoided in the development of systems where assured behaviour is required for security, safety, mission-critical and business-critical software. In general, this document is applicable to the software developed, reviewed or maintained for any application. Vulnerabilities described in this document present the way that the vulnerability described in ISO/IEC TR 24772-1 are manifested in Ada.

Technical report
45 pages
English language
sale 15% off

ISO

ISO/IEC TR 24772-1:2019(Main)

Programming languages — Guidance to avoiding vulnerabilities in programming languages — Part 1: Language-independent guidance

This document specifies software programming language vulnerabilities to be avoided in the development of systems where assured behaviour is required for security, safety, mission-critical and business-critical software. Language-specific descriptions of these vulnerabilities are provided in other parts of the ISO/IEC 24772 series. It is applicable to the software developed, reviewed, or maintained for any application. This document does not address software engineering and management issues such as how to design and implement programs, use configuration management tools, use managerial processes, and perform process improvement. Furthermore, the specification of properties and applications to be assured are not treated. Vulnerabilities are described in a generic manner that is applicable to a broad range of programming languages.

Technical report
166 pages
English language
sale 15% off

ISO

ISO/IEC 23270:2018(Main)

Information technology — Programming languages — C#

This specification describes the form and establishes the interpretation of programs written in the C# programming language. It describes: — The representation of C# programs; — The syntax and constraints of the C# language; — The semantic rules for interpreting C# programs; — The restrictions and limits imposed by a conforming implementation of C#. This specification does not describe — The mechanism by which C# programs are transformed for use by a data-processing system; — The mechanism by which C# applications are invoked for use by a data-processing system; — The mechanism by which input data are transformed for use by a C# application; — The mechanism by which output data are transformed after being produced by a C# application; — The size or complexity of a program and its data that will exceed the capacity of any specific data-processing system or the capacity of a particular processor; — All minimal requirements of a data-processing system that is capable of supporting a conforming implementation.

Standard
511 pages
English language
sale 15% off