CVS difference for ais/ai-00257.txt

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

--- ais/ai-00257.txt	2001/10/19 01:36:44	1.4
+++ ais/ai-00257.txt	2002/05/25 03:42:18	1.5
@@ -1,6 +1,7 @@
-!standard 13.12   (07)                                01-10-18  AI95-00257/03
+!standard 13.12   (07)                                02-05-10  AI95-00257/04
 !class amendment 01-02-12
-!status ARG approved 9-0-0  01-10-07
+!status Amendment 200Y 02-05-10
+!status ARG Approved 9-0-0  01-10-07
 !status work item 01-02-12
 !status received 01-02-12
 !priority Low
@@ -10,6 +11,7 @@
 !summary
 
 The following restrictions identifiers exist:
+
     No_Implementation_Attributes
     No_Implementation_Pragmas
 
@@ -18,8 +20,8 @@
 Ada code containing implementation-defined attributes and pragmas is much less
 portable than code that does not contain such items. However, it is difficult
 to prove that a given piece of Ada code does not contain any
-implementation-defined items. It can be accomplished by searching for the
-names of each possible implementation-defined entity, but this is error-prone
+implementation-defined items. This can be accomplished by searching for the
+name of each possible implementation-defined entity, but this is error-prone
 and can be very time consuming if an implementation has many
 implementation-defined items.
 
@@ -33,14 +35,13 @@
     No_Implementation_Attributes
     No_Implementation_Pragmas
 
-These restrictions do not apply to partitions; a partition may include
-compilations to which these restrictions do not apply.
+These restrictions apply only to the current compilation or environment, not
+the entire partition; a partition may include compilations to which these
+restrictions do not apply.
 
 !discussion
 
-ARG approved amendments are considered "language-defined". If a user
-wishes to avoid depending on amendments, they should use pragma Feature (see
-AI-222) or other facilities defined by the implementation for that purpose.
+ARG approved amendments are considered "language-defined".
 
 Some implementation-defined pragma arguments are common (for instance, the
 convention "StdCall" on Windows). If the No_Implementation_Pragmas applied
@@ -56,17 +57,14 @@
 
 No_Implementation_Attributes
 
-There are no implementation-defined attributes. This restriction does not apply
-to partitions; the partition need not obey the restriction even if this
-restriction applies to some compilation unit included in the partition
-(see 13.12).
+There are no implementation-defined attributes. This restriction applies only
+to the current compilation or environment, not the entire partition.
 
 No_Implementation_Pragmas
 
 There are no implementation-defined pragmas or pragma arguments. This
-restriction does not apply to partitions; the partition need not obey the
-restriction even if this restriction applies to some compilation unit included
-in the partition (see 13.12).
+restriction applies only to the current compilation or environment, not the
+entire partition.
 
 !example
 
@@ -79,15 +77,13 @@
 restrictions are defined in the Specialized Needs Annexes):
 
 @xhang<@xterm<No_Implementation_Attributes>
-There are no implementation-defined attributes. This restriction does not apply
-to partitions; the partition need not obey the restriction even if this
-restriction applies to some compilation unit included in the partition.>
+There are no implementation-defined attributes. This restriction applies only
+to the current compilation or environment, not the entire partition.>
 
 @xhang<@xterm<No_Implementation_Pragmas>
 There are no implementation-defined pragmas or pragma arguments. This
-restriction does not apply to partitions; the partition need not obey the
-restriction even if this restriction applies to some compilation unit included
-in the partition.>
+restriction applies only to the current compilation or environment, not the
+entire partition.>
 
 !ACATS test
 

Questions? Ask the ACAA Technical Agent