ISO IEC 13886-1996 Information technology - Language-Independent Procedure Calling (LIPC)《信息技术 独立于语言的过程调用(LIPC)》.pdf

1、INTERNATIONAL STANDARD ISO/IEC 13886 First edition 1996-03-I 5 Information technology - Language- Independent Procedure Calling (LIPC) Technologies de /information - Appel de pro l the minimum requirements of a data processing system that is capable of supporting an implementation of a language proc

2、essor 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

3、 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 def

4、ined by this Interna- tional Standard and the RPC standard. 2 Normative References The following standards contain provisions which, through reference in this text, constitute pro- visions of this International Standard. At the time of publication, the editions indicated were valid. All standards ar

5、e 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 IX! and IS0 maintain registers of current valid Interna- tional Standards. 1 ISO/IEC 1

6、3886:1996(E) ISO/IEC IS0 237511985, Data processing - Procedure for registration of escape sequences. ISOAEC 10646-1:1993, Information technology - Universal Multiple-Octet Coded Character Set (UCS) - Part 1: Architecture and Basic Multilingual Plane. ISO/IEC 11404:1996, Information technology - Pro

7、gramming languages, their environments and system software interfaces -Language-independent datatypes. ISO/IEC 8824-1:1995, Information technology - Abstract Syntax Notation One (ASN.1): Specification of basic notation. ISOAEC 8825-111995, Information technology - ASN.1 encoding rules: Specification

8、 of Basic Encoding Rules (BER), Canonical Encoding Rules (CER) and Distinguished Encoding Rules (DER). 3 Definitions and Abbreviations 3.1 Definitions For the purposes of this International Standard, the following definitions apply. 3.1.1 actual parameter: A value that is bound to a formal parameter

9、 during the execution of a procedure. 3.1.2 association: Any mapping from a set of symbols to values. 3.1.3 box: A model of a variable or container that holds a value of a particular type. 3.1.4 client interface binding: The possession by the client procedure of an interface reference. 3.1.5 client

10、procedure: A sequence of instructions which invokes another procedure. 3.1.6 complete procedure closure: A procedure closure, all of whose global symbols are mapped. 3.1.7 configuration: Host and target computers, any operating system(s) and software used to operate a processor. 3.1.8 execution sequ

11、ence: A succession of global states sr, sz, . . . where each state beyond the first is derived from the preceding one by a single create operation or a single write operation. 3.1.9 formal parameter: The name symbol of a parameter used in the definition of a procedure to which a value will be bound

12、during execution. 3.1.10 global state: The set of all existing boxes and their currently assigned values. 3.1.11 global symbol: Symbol used to refer to values that are permanently associated with a procedure. 3.1.12 implementation defined: An implementation defined feature is a feature that is left

13、implementation dependent by this International Standard, but any implementation claiming conformity to this International Standard shall explicitly specify how this feature is provided. 2 ISO/IEC ISO/IEC 13886: 1996(E) 3.1.13 implementation dependent: An implementation dependent feature is a feature

14、 which shall be provided by an implementation claiming conformity to this International Standard, but the implementation need not to specify how the feature is provided. 3.1.14 input parameter: A formal parameter with an attribute indicating that the corre- sponding actual parameter is to be made av

15、ailable to the server procedure on entry from the client procedure. 3.1.15 input/output parameter: A formal parameter with an attribute indicating that the corresponding actual parameters are made available to the server procedure on entry from the client procedure and to the client procedure on ret

16、urn from the server procedure. 3.1.16 interface closure: A collection of names and a collection of procedure closures, with a mapping between them. 3.1.17 interface execution context: The union of the procedure execution contexts for a given interface closure. 3.1.18 interface reference: An identifi

17、er that denotes a particular interface instance. 3.1.19 interface type: A collection of names and a collection of procedure types, with a mapping between them. 3.1.20 interface type identifier: An identifier that denotes an interface type. 3.1.21 invocation association: The invocation association of

18、 a procedure closure applied to a set of actual parameter values is the association of the closure augmented by a mapping of all local symbols to values and all formal parameter symbols to the corresponding actual parameter values. Thus it is a binding to values of all symbols in the procedure image

19、 for the duration of the invocation. 3.1.22 invocation context: For a particular procedure call, the instance of the objects referenced by the procedure, where the lifetime of the objects is bounded by the lifetime of the call. 3.1.23 marshalling: A process of collecting actual parameters, possibly

20、converting them, and assembling them for transfer. 3.1.24 output parameter: A formal parameter with an attribute indicating that the corre- sponding actual parameter is to be made available to the client procedure on return from the server procedure. 3.1.25 parameter: A parameter is used to communic

21、ate a value from a client to a server procedure. The value supplied by the client is the actual parameter, the formal parameter is used to identify the received value in the server procedure. 3.1.26 partial procedure closure: A procedure closure, some of whose global symbols are not mapped. Procedur

22、e closures may be complete, with all global symbols mapped, or partial with one or more global symbols not mapped. 3.1.27 procedure: The procedure value. 3.1.28 procedure call: The act of invoking a procedure. 3.1.29 procedure closure: A pair where the association defines the mapping for the images global symbols and no others. 3