《ISO-8652-AMD-1-2007.pdf》由会员分享，可在线阅读，更多相关《ISO-8652-AMD-1-2007.pdf（322页珍藏版）》请在三一文库上搜索。
1、 Reference number ISO/IEC 8652:1995/Amd.1:2007(E) ISO/IEC 2007 INTERNATIONAL STANDARD ISO/IEC 8652 Second edition 1995-02-15 AMENDMENT 1 2007-03-15 Information technology Programming languages Ada AMENDMENT 1 Technologies de linformation Langages de programmation Ada AMENDEMENT 1 Copyright Internati
2、onal Organization for Standardization Provided by IHS under license with ISO Licensee=IHS Employees/1111111001, User=Wing, Bernie Not for Resale, 05/08/2007 06:28:29 MDTNo reproduction or networking permitted without license from IHS -,-,- ISO/IEC 8652:1995/Amd.1:2007(E) PDF disclaimer This PDF file
3、 may contain embedded typefaces. In accordance with Adobes licensing policy, this file may be printed or viewed but shall not be edited unless the typefaces which are embedded are licensed to and installed on the computer performing the editing. In downloading this file, parties accept therein the r
4、esponsibility of not infringing Adobes licensing policy. The ISO Central Secretariat accepts no liability in this area. Adobe is a trademark of Adobe Systems Incorporated. Details of the software products used to create this PDF file can be found in the General Info relative to the file; the PDF-cre
5、ation parameters were optimized for printing. Every care has been taken to ensure that the file is suitable for use by ISO member bodies. In the unlikely event that a problem relating to it is found, please inform the Central Secretariat at the address given below. ISO/IEC 2007 All rights reserved.
6、Unless otherwise specified, no part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from either ISO at the address below or ISOs member body in the country of the requester. I
7、SO copyright office Case postale 56 CH-1211 Geneva 20 Tel. + 41 22 749 01 11 Fax + 41 22 749 09 47 E-mail copyrightiso.org Web www.iso.org Published in Switzerland ii ISO/IEC 2007 All rights reserved Copyright International Organization for Standardization Provided by IHS under license with ISO Lice
8、nsee=IHS Employees/1111111001, User=Wing, Bernie Not for Resale, 05/08/2007 06:28:29 MDTNo reproduction or networking permitted without license from IHS -,-,- ISO/IEC 8652:1995/Amd.1:2007(E) ISO/IEC 2007 All rights reserved iii Foreword ISO (the International Organization for Standardization) and IE
9、C (the International Electrotechnical Commission) form the specialized system for worldwide standardization. National bodies that are members of ISO or IEC participate in the development of International Standards through technical committees established by the respective organization to deal with p
10、articular fields of technical activity. ISO and IEC technical committees collaborate in fields of mutual interest. Other international organizations, governmental and non-governmental, in liaison with ISO and IEC, also take part in the work. In the field of information technology, ISO and IEC have e
11、stablished a joint technical committee, ISO/IEC JTC 1. International Standards are drafted in accordance with the rules given in the ISO/IEC Directives, Part 2. The main task of the joint technical committee is to prepare International Standards. Draft International Standards adopted by the joint te
12、chnical committee are circulated to national bodies for voting. Publication as an International Standard requires approval by at least 75 % of the national bodies casting a vote. Amendment 1 to ISO/IEC 8652:1995 was prepared by Joint Technical Committee ISO/IEC JTC 1, Information technology, Subcomm
13、ittee SC 22, Programming languages, their environments and system software interfaces. Amendment 1 cancels and replaces those portions of ISO/IEC 8652:1995 as corrected by Technical Corrigendum 1 ISO/IEC 8652:1995/Cor.1:2001 as specified by the body of this amendment. Those portions of the Internati
14、onal Standard as corrected by Technical Corrigendum 1 not modified by this amendment remain in force. The main emphasis of Amendment 1 is to improve the object-oriented programming and the real-time features of ISO/IEC 8652:1995 while also strengthening reliability. As in ISO/IEC 8652:1995, Annexes
15、A to J form an integral part of the International Standard as amended. Annexes K to Q are for information only. Copyright International Organization for Standardization Provided by IHS under license with ISO Licensee=IHS Employees/1111111001, User=Wing, Bernie Not for Resale, 05/08/2007 06:28:29 MDT
16、No reproduction or networking permitted without license from IHS -,-,- ISO/IEC 8652:1995/Amd.1:2007(E) iv ISO/IEC 2007 All rights reserved Introduction International Standard ISO/IEC 8652:1995 defines the Ada programming language. This amendment modifies Ada by making changes and additions that impr
17、ove: The safety of applications written in Ada; The portability of applications written in Ada; Interoperability with other languages and systems; and Accessibility and ease of transition from idioms in other programming and modeling languages. This amendment incorporates the following major additio
18、ns to the International Standard: Support for the entire ISO/IEC 10646:2003 character repertoire, both in program text and executing programs (see subclauses 2.1, 3.5.2, 3.6.3, A.1, A.3, and A.4); Interfaces, to provide a limited form of multiple inheritance of operations (see 3.9.4); Improvements f
19、or access types, such as null excluding subtypes (see 3.10), additional uses for anonymous access types (see 3.6 and 8.5.1), and anonymous access-to-subprogram subtypes to support “downward closures” (see 3.10 and 3.10.2); Additional context clause capabilities: limited views to allow mutually depen
20、dent types (see 3.10.1 and 10.1.2) and private with clauses that apply only in the private part of a package (see 10.1.2); Aggregates, constructor functions and constants for limited types (see 4.3.1, 6.5, and 7.5); Control of overriding to eliminate errors (see 8.3); Additional standard packages, i
21、ncluding time management (see 9.6), file directory and name management (see A.16), containers (see A.18), execution-time clocks (see D.14), timing events (see D.15), and vector and matrix operations (see G.3); A mechanism for writing C unions to make interfaces with C systems easier (see B.3.3); New
22、 task dispatching policies, including non-preemptive (see D.2.4) and earliest deadline first (see D.2.6); and The Ravenscar profile to provide a simplified tasking system for high-integrity systems (see D.13). This amendment is organized by sections corresponding to those in the International Standa
23、rd. These sections include wording changes and additions to the International Standard. Clause and subclause headings are given for each clause that contains a wording change. Clauses and subclauses that do not contain any change or addition are omitted. For each change, an anchor paragraph from the
24、 International Standard (as corrected by Technical Corrigendum 1) is given. New or revised text and instructions are given with each change. The anchor paragraph can be replaced or deleted, or text can be inserted before or after it. When a heading immediately precedes the anchor paragraph, any text
25、 inserted before the paragraph is intended to appear under the heading. Typographical conventions: Instructions about the text changes are in this font. The actual text changes are in the same fonts as the International Standard this font for text, this font for syntax, and this font for Ada source
26、code. Copyright International Organization for Standardization Provided by IHS under license with ISO Licensee=IHS Employees/1111111001, User=Wing, Bernie Not for Resale, 05/08/2007 06:28:29 MDTNo reproduction or networking permitted without license from IHS -,-,- ISO/IEC 8652:1995/Amd.1:2007(E) ISO
27、/IEC 2007 All rights reserved 1 Information technology Programming languages Ada AMENDMENT 1 Introduction Of International Standard ISO/IEC 8652:1995. Modifications of this section of that International Standard are found here. Replace paragraph 3: Rationale for the Ada Programming Language - 1995 e
28、dition, which gives an introduction to the new features of Ada, and explains the rationale behind them. Programmers should read this first. by: Ada 95 Rationale. This gives an introduction to the new features of Ada incorporated in the 1995 edition of this Standard, and explains the rationale behind
29、 them. Programmers unfamiliar with Ada 95 should read this first. Ada 2005 Rationale. This gives an introduction to the changes and new features in Ada 2005 (compared with the 1995 edition), and explains the rationale behind them. Programmers should read this rationale before reading this Standard i
30、n depth. Replace paragraph 5: The Annotated Ada Reference Manual (AARM). The AARM contains all of the text in the RM95, plus various annotations. It is intended primarily for compiler writers, validation test writers, and others who wish to study the fine details. The annotations include detailed ra
31、tionale for individual rules and explanations of some of the more arcane interactions among the rules. by: The Annotated Ada Reference Manual (AARM). The AARM contains all of the text in the consolidated Ada Reference Manual, plus various annotations. It is intended primarily for compiler writers, v
32、alidation test writers, and others who wish to study the fine details. The annotations include detailed rationale for individual rules and explanations of some of the more arcane interactions among the rules. Replace paragraph 6: Ada was originally designed with three overriding concerns: program re
33、liability and maintenance, programming as a human activity, and efficiency. This revision to the language was designed to provide greater flexibility and extensibility, additional control over storage management and synchronization, and standardized packages oriented toward supporting important appl
34、ication areas, while at the same time retaining the original emphasis on reliability, maintainability, and efficiency. by: Ada was originally designed with three overriding concerns: program reliability and maintenance, programming as a human activity, and efficiency. The 1995 revision to the langua
35、ge was designed to provide greater flexibility and extensibility, additional control over storage management and synchronization, and standardized packages oriented toward supporting important application areas, while at the same time retaining the original emphasis on reliability, maintainability,
36、and efficiency. This amended version provides further flexibility and adds more standardized packages within the framework provided by the 1995 revision. Copyright International Organization for Standardization Provided by IHS under license with ISO Licensee=IHS Employees/1111111001, User=Wing, Bern
37、ie Not for Resale, 05/08/2007 06:28:29 MDTNo reproduction or networking permitted without license from IHS -,-,- ISO/IEC 8652:1995/Amd.1:2007(E) 2 ISO/IEC 2007 All rights reserved Replace paragraph 32: An enumeration type defines an ordered set of distinct enumeration literals, for example a list of
38、 states or an alphabet of characters. The enumeration types Boolean, Character, and Wide_Character are predefined. by: An enumeration type defines an ordered set of distinct enumeration literals, for example a list of states or an alphabet of characters. The enumeration types Boolean, Character, Wid
39、e_Character, and Wide_Wide_Character are predefined. Replace paragraph 34: Composite types allow definitions of structured objects with related components. The composite types in the language include arrays and records. An array is an object with indexed components of the same type. A record is an o
40、bject with named components of possibly different types. Task and protected types are also forms of composite types. The array types String and Wide_String are predefined. by: Composite types allow definitions of structured objects with related components. The composite types in the language include
41、 arrays and records. An array is an object with indexed components of the same type. A record is an object with named components of possibly different types. Task and protected types are also forms of composite types. The array types String, Wide_String, and Wide_Wide_String are predefined. Insert a
42、fter paragraph 38: From any type a new type may be defined by derivation. A type, together with its derivatives (both direct and indirect) form a derivation class. Class-wide operations may be defined that accept as a parameter an operand of any type in a derivation class. For record and private typ
43、es, the derivatives may be extensions of the parent type. Types that support these object-oriented capabilities of class-wide operations and type extension must be tagged, so that the specific type of an operand within a derivation class can be identified at run time. When an operation of a tagged t
44、ype is applied to an operand whose specific type is not known until run time, implicit dispatching is performed based on the tag of the operand. the new paragraph: Interface types provide abstract models from which other interfaces and types may be composed and derived. This provides a reliable form
45、 of multiple inheritance. Interface types may also be implemented by task types and protected types thereby enabling concurrent programming and inheritance to be merged. Replace paragraph 41: Representation clauses can be used to specify the mapping between types and features of an underlying machin
46、e. For example, the user can specify that objects of a given type must be represented with a given number of bits, or that the components of a record are to be represented using a given storage layout. Other features allow the controlled use of low level, nonportable, or implementation-dependent asp
47、ects, including the direct insertion of machine code. by: Aspect clauses can be used to specify the mapping between types and features of an underlying machine. For example, the user can specify that objects of a given type must be represented with a given number of bits, or that the components of a
48、 record are to be represented using a given storage layout. Other features allow the controlled use of low level, nonportable, or implementation-dependent aspects, including the direct insertion of machine code. Replace paragraph 42: The predefined environment of the language provides for input-outp
49、ut and other capabilities (such as string manipulation and random number generation) by means of standard library packages. Input-output is supported for values of user-defined as well as of predefined types. Standard means of representing values in display form are also provided. Other standard librar