- 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.
- The form of a pragma Shared_Passive is as follows:
- A shared passive library unit is a library unit to which a Shared_Passive
pragma applies. The following restrictions apply to such a library unit:
- it shall depend semantically only upon declared pure or shared
passive library units;
- it shall not contain a library-level declaration of an access
type that designates a class-wide type, task type, or protected
type with entry_declarations; if the shared passive library unit
is generic, it shall not contain a declaration for such an access
type unless the declaration is nested within a body other than a
- 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.
- A shared passive library unit is preelaborated.
- A shared passive library unit shall be assigned to at most one partition
within a given program.
- 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.
-- Email comments, additions, corrections, gripes, kudos, etc. to:
Page last generated: 95-03-12