CVS difference for ais/ai-00245.txt

Differences between 1.2 and version 1.3
Log of other versions for file ais/ai-00245.txt

--- ais/ai-00245.txt	2000/11/04 01:10:29	1.2
+++ ais/ai-00245.txt	2004/04/06 19:56:59	1.3
@@ -1,5 +1,6 @@
-!standard 10.1.4  (07)                                 00-10-30  AI95-00245/01
+!standard 10.1.4  (07)                                 04-03-24  AI95-00245/02
 !class confirmation 00-10-30
+!status ARG Approved 8-0-1  04-03-05
 !status work item 00-10-30
 !status received 00-10-30
 !qualifier Clarification
@@ -10,14 +11,14 @@
 !summary
 
 The implementation must insure that a partition containing inlined subprograms
-is consistent. It can do this by requiring recompilation of units, or via a
+is consistent. It can do this by requiring recompilation of units, or via an
 automatic recompilation mechanism.
 
 !question
 
 Consider a package P that contains explicitly inlined subprograms,
 and a main subprogram Q that is compiled after P's body and calls such
-subprograms.  P's body is later changed and recompiled without any
+subprograms. P's body is later changed and recompiled without any
 subsequent user actions causing Q to be recompiled or Q's code to be
 regenerated.
 
@@ -26,9 +27,9 @@
 program may be rejected.)
 
 Apparently, the obsolete version of P's body is not needed in the program
-because there is no semantic dependence on it, see 10.2(4).  And the
+because there is no semantic dependence on it, see 10.2(4). And the
 permission to remove Q from the environment when P's body is recompiled,
-see 10.1.4(7), is simply a permission.  There are rules to prevent multiple
+see 10.1.4(7), is simply a permission. There are rules to prevent multiple
 versions of a compilation unit in a program, see 10.1.4(5), but they don't
 seem to help here because they are based on semantic dependence, and they
 are compile-time rules.

Questions? Ask the ACAA Technical Agent