This International Standard specifies the form and meaning of programs written inAda. Its purpose is to promote the portability of Ada programs to a variety ofdata processing systems.
1 Extent
This International Standard specifies:
· The form of a program written in Ada;
· The effect of translating and executing such a program;
· The manner in which program units may be combined to form Ada programs;
· The language-defined library units that a conforming implementation is requiredto supply;
· The permissible variations within the standard, and the manner in which theyare to be documented;
· Those violations of the standard that a conforming implementation is requiredto detect, and the effect of attempting to translate or execute a programcontaining such violations;
· Those violations of the standard that a conforming implementation is notrequired to detect.
This International Standard does not specify:
· The means whereby a program written in Ada is transformed into object codeexecutable by a processor;
· The means whereby translation or execution of programs is invoked and theexecuting units are controlled;
· The size or speed of the object code, or the relative execution speed ofdifferent language constructs;
· The form or contents of any listings produced by implementations; inparticular, 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 aparticular conforming implementation.
2 Structure
This International Standard contains thirteen sections, fourteen annexes, and anindex.
The core of the Ada language consists of:
· Sections 1 through 13
· Annex A, "Predefined Language Environment"
· Annex B, "Interface to Other Languages"
· Annex J, "Obsolescent Features"
The following Specialized Needs Annexes define features that are needed by certainapplication areas:
· Annex C, "Systems Programming"
· Annex D, "Real-Time Systems"
· Annex E, "Distributed Systems"
· Annex F, "Information Systems"
· Annex G, "Numerics"
· Annex H, "Safety and Security"
The core language and the Specialized Needs Annexes are normative, except that thematerial in each of the items listed below is informative:
· Text under a NOTES or Examples heading.
· Each clause or subclause whose title starts with the word "Example" or"Examples".
All implementations shall conform to the core language. In addition, animplementation may conform separately to one or more Specialized Needs Annexes.
The following Annexes are informative:
· Annex K, "Language-Defined Attributes"
· Annex L, "Language-Defined Pragmas"
· Annex M, "Implementation-Defined Characteristics"
· Annex N, "Glossary"
· Annex P, "Syntax Summary"
Each section is divided into clauses and subclauses that have a common structure. Each section, clause, and subclause first introduces its subject. After theintroductory text, text is labeled with the following headings:
Syntax
Syntax rules (indented).
Name Resolution Rules
Compile-time rules that are used in name resolution, including overloadresolution.
Legality Rules
Rules that are enforced at compile time. A construct is legal if it obeys all ofthe Legality Rules.
Static Semantics
A definition of the compile-time effect of each construct.
Post-Compilation Rules
Rules that are enforced before running a partition. A partition is legal if itscompilation units are legal and it obeys all of the Post-Compilation Rules.
Dynamic Semantics
A definition of the run-time effect of each construct.
Bounded (Run-Time) Errors
Situations that result in bounded (run-time) errors (see 1.1.5).
Erroneous Execution
Situations that result in erroneous execution (see 1.1.5).
Implementation Requirements
Additional requirements for conforming implementations.
Documentation Requirements
Documentation requirements for conforming implementations.
Metrics
Metrics that are specified for the time/space properties of the execution ofcertain language cons
ISO/IEC 8652:1995 history
2023ISO/IEC 8652:2023 Information technology — Programming languages — Ada