Ada Conformity Assessment Authority      Home Conformity Assessment   Test Suite ARGAda Standard
 
Annotated Ada Reference Manual (Ada 202x Draft 22)Legal Information
Contents   Index   References   Search   Previous   Next 

E.2.1 Shared Passive Library Units

1
[A shared passive library unit is used for managing global data shared between active partitions. The restrictions on shared passive library units prevent the data or tasks of one active partition from being accessible to another active partition through references implicit in objects declared in the shared passive library unit.] 

Language Design Principles

1.a
The restrictions governing a shared passive library unit are designed to ensure that objects and subprograms declared in the package can be used safely from multiple active partitions, even though the active partitions live in different address spaces, and have separate run-time systems. 

Syntax

2
The form of a pragma Shared_Passive is as follows: 
3
  pragma Shared_Passive[(library_unit_name)];

Legality Rules

4/3
{AI05-0243-1} A pragma Shared_Passive is used to specify that a library unit is a shared passive library unit, namely that the Shared_Passive aspect of the library unit is True. The following restrictions apply to such a library unit:
4.a/3
Aspect Description for Shared_Passive: A given package is used to represent shared memory in a distributed system.
5
[it shall be preelaborable (see 10.2.1);]
5.a
Ramification: It cannot contain library-level declarations of protected objects with entries, nor of task objects. Task objects are disallowed because passive partitions don't have any threads of control of their own, nor any run-time system of their own. Protected objects with entries are disallowed because an entry queue contains references to calling tasks, and that would require in effect a pointer from a passive partition back to a task in some active partition.
6/3
{AI05-0243-1} it shall depend semantically only upon declared pure or shared passive library_items;
6.a
Reason: Shared passive packages cannot depend semantically upon remote types packages because the values of an access type declared in a remote types package refer to the local heap of the active partition including the remote types package. 
6.b/3
Ramification: {AI05-0243-1} We say library_item here, so that limited views are allowed; those are not library units, but they are library_item.
7/5
{8652/0080} {AI95-00003-01} {AI12-0038-1} {AI12-0320-1} it shall not contain a library-level declaration: of an access type that designates a class-wide type, nor a type with a part that is of a task type, or protected type with entry_declarations;.
7.1/5
{AI12-0320-1} of an access type that designates a class-wide type; 
7.a
Reason: These kinds of access types are disallowed because the object designated by an access value of such a type could contain an implicit reference back to the active partition on whose behalf the designated object was created. 
7.2/5
{AI12-0320-1} of a type with a part that is of a task type;
7.3/5
{AI12-0320-1} of a type with a part that is of a protected type with entry_declarations; nor
7.4/5
{AI12-0038-1} {AI12-0320-1} it shall not contain a library-level declaration that contains a name that denotes a type declared within a declared-pure package, if that type has a part that is of an access type; for the purposes of this rule, the parts considered include those of the full views of any private types or private extensions.
7.b/4
Reason: This rule breaks privacy by looking into the full views of private types. Avoiding privacy breakage here would have required disallowing the use in a shared passive package of any private type declared in a declared-pure package, which would have been severely incompatible. 
8
Notwithstanding the definition of accessibility given in 3.10.2, the declaration of a library unit P1 is not accessible from within the declarative region of a shared passive library unit P2, unless the shared passive library unit P2 depends semantically on P1. 
8.a
Discussion: We considered a more complex rule, but dropped it. This is the simplest rule that recognizes that a shared passive package may outlive some other library package, unless it depends semantically on that package. In a nondistributed program, all library packages are presumed to have the same lifetime.
8.b
Implementations may define additional pragmas that force two library packages to be in the same partition, or to have the same lifetime, which would allow this rule to be relaxed in the presence of such pragmas. 

Static Semantics

9
A shared passive library unit is preelaborated.

Post-Compilation Rules

10
A shared passive library unit shall be assigned to at most one partition within a given program.
11
Notwithstanding the rule given in 10.2, a compilation unit in a given partition does not need (in the sense of 10.2) the shared passive library units on which it depends semantically to be included in that same partition; they will typically reside in separate passive partitions.

Wording Changes from Ada 95

11.a/2
{8652/0080} {AI95-00003-01} Corrigendum: Corrected the wording to allow access types in blocks in shared passive generic packages. 

Extensions to Ada 2005

11.b/3
{AI05-0243-1} Shared_Passive is now a categorization aspect, so it can be specified by an aspect_specification — although the pragma is still preferred by the Standard. 

Incompatibilities With Ada 2012

11.c/4
{AI12-0038-1} Corrigendum: Uses of access types declared in declared-pure units are not allowed in library-level shared passive packages. These were allowed by Ada 2005 and Ada 2012, but it is unlikely that they work properly, as active partitions could disappear before the shared-passive partition. As such, the new errors are more likely to catch bugs than to cause them. 

Contents   Index   References   Search   Previous   Next 
Ada-Europe Ada 2005 and 2012 Editions sponsored in part by Ada-Europe