Go to the first, previous, next, last section, table of contents.

E.2.3 Remote Call Interface Library Units

  1. A remote call interface library unit can be used as an interface for remote procedure calls (RPCs) (or remote function calls) between active partitions.

    Syntax

  2. The form of a pragma Remote_Call_Interface is as follows: 
  3. pragma Remote_Call_Interface[(library_unit_name)];
  4. The form of a pragma All_Calls_Remote is as follows: 
  5. pragma All_Calls_Remote[(library_unit_name)];
    1. A pragma All_Calls_Remote is a library unit pragma.

Legality Rules

  1. A remote call interface (RCI) is a library unit to which the pragma Remote_Call_Interface applies. A subprogram declared in the visible part of such a library unit is called a remote subprogram.
  2. The declaration of an RCI library unit shall be preelaborable, See section 10.2.1 Elaboration Control, and shall depend semantically only upon declared pure, shared passive, remote types, or other remote call interface library units.
  3. In addition, the following restrictions apply to the visible part of an RCI library unit:
    1. it shall not contain the declaration of a variable;
    2. it shall not contain the declaration of a limited type;
    3. it shall not contain a nested generic_declaration;
    4. it shall not contain the declaration of a subprogram to which a pragma Inline applies;
    5. it shall not contain a subprogram (or access-to-subprogram) declaration whose profile has an access parameter, or a formal parameter of a limited type unless that limited type has user-specified Read and Write attributes;
    6. any public child of the library unit shall be a remote call interface library unit.

  1. If a pragma All_Calls_Remote applies to a library unit, the library unit shall be a remote call interface.

    Post-Compilation Rules

  2. A remote call interface library unit shall be assigned to at most one partition of a given program. A remote call interface library unit whose parent is also an RCI library unit shall be assigned only to the same partition as its parent.
  3. Notwithstanding the rule given in See section 10.2 Program Execution, a compilation unit in a given partition that semantically depends on the declaration of an RCI library unit, needs (in the sense of See section 10.2 Program Execution.) only the declaration of the RCI library unit, not the body, to be included in that same partition. Therefore, the body of an RCI library unit is included only in the partition to which the RCI library unit is explicitly assigned.

    Implementation Requirements

  4. If a pragma All_Calls_Remote applies to a given RCI library package, then the implementation shall route any call to a subprogram of the RCI package from outside the declarative region of the package through the Partition Communication Subsystem (PCS); See section E.5 Partition Communication Subsystem. Calls to such subprograms from within the declarative region of the package are defined to be local and shall not go through the PCS.

    Implementation Permissions

  5. An implementation need not support the Remote_Call_Interface pragma nor the All_Calls_Remote pragma. Explicit message-based communication between active partitions can be supported as an alternative to RPC.

Go to the first, previous, next, last section, table of contents.