1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
|
@comment{ $Source: e:\\cvsroot/ARM/Source/pre_ada.mss,v $ }
@comment{ $Revision: 1.15 $ $Date: 00/03/08 Created by RLB to avoid Includes }
@Part(predefstandard, Root="ada.mss")
@Comment{$Date: 2000/08/31 04:56:06 $}
@LabeledClause{The Package Ada}
@begin{StaticSem}
@Leading@keepnext@;The following language-defined library package exists:
@begin{Example}
@RootLibUnit{Ada}@key[package] Ada @key[is]
@key[pragma] Pure(Ada);
@key[end] Ada;
@end{Example}
Ada serves as the parent of most of the other language-defined library
units; its declaration is empty (except for the @nt{pragma} Pure).
@end{StaticSem}
@begin{Legality}
In the standard mode, it is illegal to compile a child of package
Ada.
@begin{Reason}
The intention is that mentioning, say, Ada.Text_IO in a
@nt{with_clause} is guaranteed (at least in the standard mode) to refer
to the standard version of Ada.Text_IO.
The user can compile a root library unit Text_IO that has no relation to
the standard version of Text_IO.
@end{Reason}
@begin{Ramification}
Note that Ada can have non-language-defined grandchildren,
assuming the implementation allows it.
Also, packages System and Interfaces can have children,
assuming the implementation allows it.
@end{Ramification}
@begin{ImplNote}
An implementation will typically support a nonstandard mode in
which compiling the language defined library units is allowed.
Whether or not this mode is made available to users is up to the
implementer.
An implementation could theoretically have private children of
Ada, since that would be semantically neutral.
However, a programmer cannot compile such a library unit.
@end{ImplNote}
@end{Legality}
@begin{Extend83}
@Defn{extensions to Ada 83}
This clause is new to Ada 95.
@end{Extend83}
|
