This is a preview - click here to buy the full publication INTERNATIONAL STANDARD

Transcription

1 INTERNATIONAL STANDARD lso/iec First edition l 5 Information technology - Language- Independent Procedure Calling (LIPC) Technologies de I information - Appel de procbdure indbpendant du langage (L/PC) Reference number ISO/lEC 13886:1996(E)

2 ISO/IEC 13886:1996(E) This is a preview - click here to buy the full publication Contents 1 Scope 2 References 3 Definitions and Abbreviations 3.1 Definitions Abbreviations Conformance 4.1 Modes of conformance Client mode conformance Server mode conformance... 5 A model of procedure calling: informal description 5.1 Model overview Parameter passing Methods of parameter passing Call by Value Sent on Initiation Call by Value Sent on Request Call by Value Returned on Termination Call by Value Returned when Available Global data Parameter Marshalling / Unmarshalling Pointer Parameters Private types Execution-time Control Terminations Normal termination Abnormal Termination External Cancellation Predefined conditions Execution Control Synchronous and Asynchronous Calling Recursion... 6 A model of procedure calling: formal description 6.1 Value ISO/IEC 1996 All rights reserved. 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 the publisher. ISO/IEC Copyright Office l Case postale 56 l CH-1211 Geneve 20 l Switzerland Printed in Switzerland 11

3 ISO/IEC 13886: 1996(E) 6.2 Boxes and global state Symbol Procedure image Association Procedure closures Boxes, pointers, values, and datatypes Interface closure Interfacetype Specifications Basic procedure invocation Type correctness Associates Simple Associates Generalized Associates Execution and Invocation contexts Parameter translations Defining Translation Procedures Interface Definition Notation Definitional Conventions Character Set Formal Syntax Whitespace Interface Type Declarations Type references Value References Import Declarations Value Declarations Datatype Declarations Primitive Datatypes Integer The real datatype The character datatype The boolean datatype The enumerated datatype The octet datatype The procedure datatype The state datatype The ordinal datatype The time datatype The bit datatype The rational datatype The scaled datatype The complex datatype The void datatype Generated datatypes The record datatype The choice datatype

4 ISO/IEC 13886:1996(E) The array datatype The pointer datatype Subtypes Parameterized Types Identifiers Value references to fields Value references to parameters, return-args, or to fields contained within them Value references to formal-value-parms Value references to value-expressions Value references to enumeration-identifiers Termination references Annexes A Procedure Parameters 45 A.1 LIPC Reference / Local Access A.2 LIPC! Reference / LIPC Access A.3 Local Reference / Local Access B Interface Definition Notation Syntax 47 C How to do an LIPC binding for a language 53 C.1 Linking the client and the server C.2 Client mode binding C.3 Server mode binding C.4 Procedure parameters C.5 Global variables D LIPC IDN - RPC IDL Alignment overview 58 D.l Interface Declarations D.l.l Attributes D.l.2 Imports Clause D.2 Other Declarations D.2.1 Type Declarations D.2.2 Value Declarations D.2.3 Procedure Declarations D.2.4 Termination Declarations D.3 Primitive Datatypes D.3.1 Boolean D.3.2 State D.3.3 Enumerated D.3.4 Character D.3.5 Ordinal D.3.6 Time D.3.7 Integer D.3.8 Rational D.3.9 Scaled D.3.10 Real iv

5 ISO/IEC 13886: 1996(E) D.3.11Complex D.3.12Void D.4 Type Qualifiers D.5 Generated Datatypes D.5.1 Choice D.5.2 Pointer D.5.3 Procedure D.6 Aggregate Datatypes D.6.1 Record D.6.2 Set D.6.3 Bag D.6.4 Sequence D.6.5 Array D.6.6 Table D.7 Derived Datatypes and Generators D.7.1 Naturalnumber D.7.2 Modulo D.7.3 Bit D.7.4 Bitstring D.7.5 Characterstring D.7.6 Timeinterval D.7.7 Octet D.7.8 Octetstring D.7.9 Private D.8 Other RPC Datatypes D.9. Dependent Values D.10 Cross References V

6 ISO/IEC 13886:1996(E) Foreword IS0 (the International Organization for Standardization) and IEC (the International Electrotechnical Commission) form the specialized system for worldwide standardization. National bodies that are members of IS0 or IEC participate in the development of International Standards through technical committees established by the respective organizations to deal with particular fields of technical activity. IS0 and IEC technical committees collaborate in fields of mutual interest. Other international organizations, governmental and non-governmental, in liaison with IS0 and IEC, also take part in the work. In the field of information technology, IS0 and IEC have established a joint technical committee, ISO/IEC JTC 1. Draft International Standards adopted by the joint technical cotittee 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. International Standard ISO/IEC was prepared by Joint Technical Committee ISO/IEC JTC 1, Information technology, Subcommittee SC 22, Programming languages, their environments and system software interfaces. Annexes A to D of this International Standard are for information only. vi

7 ISO/IEC 13886: 1996(E) Introduction The purpose of this International Standard is to provide a common model for language standards for the concept of procedure calling. It is an enabling standard to aid in the development of languageindependent tools and services, common procedure libraries and mixed language programming. In mixed language applications, server procedures would execute on language processors operating in server mode, and the procedures would be called from language processors operating in client mode. Note that the languages need not be different, and if the processors are the same the model collapses into conventional single processor programming. Most programming languages include the concepts of procedures and their invocation. The main variance between the methods used in various programming languages lies in the ways parameters are passed between the client and server procedures. Procedure calling is a simple concept at the functional level, but the interaction of procedure calling with datatyping and program structure along with the many variations on procedure calling and restrictions on calling that are applied by various programmin g languages transforms the seemingly simple concept of procedure calling into a more complex feature of programming languages. The need for a standard model for procedure calling is evident from the multitude of variants of procedure calling in the standardized languages. The existence of this International Standard for Language-Independent Procedure Calling (LIPC) d oes not require that all programming languages should adopt this model as their sole means of procedure calling. The nominal requirement is for programming languages to provide a mapping to LIPC from their native procedure calling mechanism, and to be able to accept calls from other programmin g languages who have defined a mapping to this International Standard. This International Standard is a specification of a common model for procedure calling. It is not intended to be a specification of how an implementation of the LIPC is to be provided. Also, it is important to note that it does not address the question of how the procedure call initiated by the client mode processor is communicated to the server mode processor, or how the results are returned. The model defined in this International Standard is intended for use by languages so that they may provide standard mappings from their native procedure model. This International Standard depends on the International Standard for Language-Independent Datatypes, ISO/IEC 104, for the definition of the datatypes that are to be supported in the model for LIPC that it provides. vii

8 INTERNATIONAL STANDARD ISO/IEC 13886:1996(E) Information technology - Language-Independent Procedure Calling (LIPC) 1 Scope This International Standard specifies a model for procedure calls, and a reference syntax for map- Pi% to and from the model. This syntax is referred to as the Interface Definition Notation. The I model defined in this International Standard includes such features as procedure invocation, parameter passing, completion status, and environmental issues relating to non-local references and state. This International Standard does not specify: l the method by which the procedure call initiated by the client mode processor is communicated to the server mode language processor; l the minimum requirements of a data processing system that is capable of supporting an implementation of a language processor to support LIPC; l the mechanism by which programs written to support LIPC are transformed for use by a data processing system; l the representation of a parameter. NOTE - Originally it was the intention to align the definitions and concepts of this International Standard with those of the RPC standard (ISO/IEC 11578). Unfortunately, in a late stage of the development process of the RPC standard it was decided to use for that standard a completely different approach. Hence the intended alignment did not materialize. Annex D gives an overview of the differences between the concepts as defined by this International Standard and the RPC standard. 2 Normative References The following standards contain provisions which, through reference in this text, constitute provisions of this International Standard. At the time of publication, the editions indicated were valid. All standards are subject to revision, and parties to agreements based on this International Standard are encouraged to investigate the possibility of applying the most recent editions of the standards indicated below. Members of IEC and IS0 maintain registers of current valid International Standards. 1

9 ISO/IEC 13886:1996(E) IS , Data processing - Procedure for registration of escape sequences. ISO/IEC! l: 1993, Information technology - Universal Multiple-Octet Coded Character Set (KS) - Part 1: Architecture and Basic Multilingual Plane. ISO/IEC 104:1996, Information technology - Programming languages, their environments and system software interfaces - Language-independent datatypes. ISO/IEC 8824-l: 1995, Information technology - Abstract Syntax Notation One (ASN. 1): Specification of basic notation. ISOIIEC 8825~1:1995, Information technology - ASN.1 encoding rules: Specification of Basic Encoding Rules (BER), Canonical Encoding Rules (CER) and Distinguished Encoding Rules (DER). 2