CVS difference for ais/ai-00212.txt

Differences between 1.5 and version 1.6
Log of other versions for file ais/ai-00212.txt

--- ais/ai-00212.txt	2002/10/29 20:24:57	1.5
+++ ais/ai-00212.txt	2002/12/04 23:43:37	1.6
@@ -1,13 +1,13 @@
-!standard 10.01.05  (09)                               02-10-23  AI95-00212/02
+!standard 10.01.05  (09)                               02-11-27  AI95-00212/03
 !class binding interpretation 99-03-26
 !status Amendment 200Y 02-10-23
-!status ARG approved 10-0-0  02-10-12
+!status ARG Approved 10-0-0  02-10-12
 !status work item 00-11-13
 !status received 98-11-21
 !priority Low
 !difficulty Medium
 !qualifier Clarification
-!subject Restrictions on configuration pragmas.
+!subject Restrictions on configuration pragmas
 
 !summary
 
@@ -56,17 +56,17 @@
 link-time check is then required upon linking the units of a partition
 to ensure the consistency of the selected options. To the extent that
 partition-wide options imply different code generation, code may need
-to be (re)generated at link-time.
+to be (re)generated at link time.
 
 It is also a good configuration management convention in environments that
 support separate libraries for separate partitions to "pre-configure" the
 library with the partition-wide option that will apply to all units compiled
 into the library. Here, enforcement of consistency and any impact on code
-generation can be accommodated at compile-time of the compilation units.
+generation can be accommodated at compile time of the compilation units.
 
 The !recommendation reflects a compromise between these two positions,
 enabling both conventions to be applied by the user without mandating
-checks and possibly code generation at link-time.
+checks and possibly code generation at link time.
 It also eliminates a portability problem with code that adheres to the
 documentation convention of including configuration pragmas with each
 unit that requires them.

Questions? Ask the ACAA Technical Agent