CVS difference for ais/ai-00048.txt
--- ais/ai-00048.txt 2000/06/21 23:39:07 1.8
+++ ais/ai-00048.txt 2000/07/15 02:29:54 1.9
@@ -130,17 +130,17 @@
@drepl
A library package or generic library package is called a @i<shared passive>
library unit if a Shared_Passive pragma applies to it. A library package or
-generic library package is called a @i<remote types> library unit if a Remote_
-Types pragma applies to it. A library package or generic library package is
-called a @i<remote call interface> if a Remote_Call_Interface pragma applies to
-it. A @i<normal library unit> is one to which no categorization pragma
+generic library package is called a @i<remote types> library unit if a
+Remote_Types pragma applies to it. A library package or generic library package
+is called a @i<remote call interface> if a Remote_Call_Interface pragma applies
+to it. A @i<normal library unit> is one to which no categorization pragma
applies.
@dby
A library package or generic library package is called a @i<shared passive>
library unit if a Shared_Passive pragma applies to it. A library package or
-generic library package is called a @i<remote types> library unit if a Remote_
-Types pragma applies to it. A library unit is called a @i<remote call interface>
-if a Remote_Call_Interface pragma applies to
+generic library package is called a @i<remote types> library unit if a
+Remote_Types pragma applies to it. A library unit is called a @i<remote call
+interface> if a Remote_Call_Interface pragma applies to
it. A @i<normal library unit> is one to which no categorization pragma
applies.
@@ -285,9 +285,9 @@
First, I don't think that the term RCI unit is defined by the language, I
guess you mean RCI library unit. E.2 (4) says: "A library generic package
-or generic library package is called remote call interface if a Remote_Call_
-Interface pragma applies to it." (and similarly for the othere categ
-pragmas). Which means the subp's cannot be RCI's. Note that this is an
+or generic library package is called remote call interface if a
+Remote_Call_Interface pragma applies to it." (and similarly for the other
+e categ pragmas). Which means the subp's cannot be RCI's. Note that this is an
unfortunate omittion in this paragraph: For all other categ pragmas, the
text says: "is called a xxxx library unit if the xxx pragma applies to it".
For some reason this is different for RCIs where it says "is called rci
@@ -328,7 +328,7 @@
> First, I don't think that the term RCI unit is
> defined by the language, I guess you mean RCI library unit. E.2 (4) says: "A
> library generic package or generic library package is called remote call
-> interface if a Remote_Call_ Interface pragma applies to it." (and similarly
+> interface if a Remote_Call_Interface pragma applies to it." (and similarly
> for the othere categ pragmas). Which means the subp's cannot be RCI's. Note
> that this is an unfortunate omittion in this paragraph: For all other categ
> pragmas, the text says: "is called a xxxx library unit if the xxx pragma
@@ -406,7 +406,7 @@
> > First, I don't think that the term RCI unit is
> > defined by the language, I guess you mean RCI library unit. E.2 (4) says: "A
> > library generic package or generic library package is called remote call
-> > interface if a Remote_Call_ Interface pragma applies to it." (and similarly
+> > interface if a Remote_Call_Interface pragma applies to it." (and similarly
> > for the othere categ pragmas). Which means the subp's cannot be RCI's.
> ...
Questions? Ask the ACAA Technical Agent