CVS difference for ais/conflict.txt

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

--- ais/conflict.txt	1999/09/16 20:40:30	1.2
+++ ais/conflict.txt	1999/10/08 23:41:06	1.3
@@ -30,6 +30,40 @@
 is finalized as part of the finalizations due to be performed for the
 object's innermost enclosing master.
 
+!corrigendum 8.03 (26)
+!AI-00044
+!AI-00150
+
+@drepl
+An explicit declaration is illegal if there is a homograph occurring
+immediately within the same declarative region that is visible at the place
+of the declaration, and is not hidden from all visibility by the explicit
+declaration. Similarly, the @fa<context_clause> for a @fa<subunit> is illegal if it
+mentions (in a @fa<with_clause>) some library unit, and there is a homograph of
+the library unit that is visible at the place of the corresponding stub, and
+the homograph and the mentioned library unit are both declared immediately
+within the same declarative region. These rules also apply to dispatching
+operations declared in the visible part of an instance of a generic unit.
+However, they do not apply to other overloadable declarations in an instance;
+such declarations may have type conformant profiles in the instance, so long
+as the corresponding declarations in the generic were not type conformant.
+@dby
+A non-overridable declaration is illegal if there is a homograph occurring
+immediately within the same declarative region that is visible at the place
+of the declaration, and is not hidden from all visibility by the non-overridable
+declaration. In addition, a type extension is illegal if somewhere within
+its immediate scope it has two visible components with the same name. Similarly,
+the @fa<context_clause> for a @fa<subunit> is illegal if it
+mentions (in a @fa<with_clause>) some library unit, and there is a homograph of
+the library unit that is visible at the place of the corresponding stub, and
+the homograph and the mentioned library unit are both declared immediately
+within the same declarative region. These rules also apply to dispatching
+operations declared in the visible part of an instance of a generic unit.
+However, they do not apply to other overloadable declarations in an instance;
+such declarations may have type conformant profiles in the instance, so long
+as the corresponding declarations in the generic were not type conformant.
+
+
 !corrigendum 8.05.04 (5)
 !AI-00135
 !AI-00145
@@ -66,8 +100,9 @@
 @dby
 For a call to a subprogram whose body is given as a renaming-as-body, the
 execution of the renaming-as-body is equivalent to the execution of a
-subprogram_body that simply calls the renamed subprogram with the same
-parameters.
+@fa<subprogram_body> that simply calls the renamed subprogram with its formal
+parameters as the actual parameters and, if a function, returns the value of
+the call.
 
 For a call on a renaming of a dispatching subprogram that is overridden,
 if the overriding occurred before the renaming, then the body executed is
@@ -80,25 +115,53 @@
 error to call that subprogram. Possible consequences are that Program_Error
 or Storage_Error is raised, or that the call results in an indefinite loop.
 
-!corrigendum 10.01.05 (9)
+!corrigendum 10.01.05 (7)
 !AI-00041
 !AI-00199
 
 @dinsa
-An implementation may place restrictions on configuration pragmas, so
-long as it allows them when the environment contains no @fa<library_item>s other
-than those of the predefined environment.
+Certain program unit pragmas are defined to be @i<library unit pragmas>. The
+name, if any, in a library unit pragma shall denote the declaration of a
+library unit.
+@dinst
+@i<@s8<Static Semantics>>
+
+A library unit pragma that applies to a generic unit does not apply to its
+instances. Any other program unit pragma that applies to a generic unit applies
+to an instance of the generic unless the instance has an overriding pragma.
+
+!corrigendum 13.01(11)
+!AI-00117
+!AI-00137
+
+@drepl
+Representation aspects of a generic formal parameter are the same as
+those of the actual. A type-related representation item is not allowed for a
+descendant of a generic formal untagged type.
+@dby
+Representation aspects of a generic formal parameter are the same as
+those of the actual. Representation aspects of a partial view are the same
+as those of the full view. A type-related representation item, other than the
+stream-oriented attributes Read, Write, Input, and Output, is not allowed
+for a descendant of a generic formal untagged type.
+
+!corrigendum 13.12(9)
+!AI-00130
+!AI-00190
+
+@dinsa
+An implementation may place limitations on the values of the @fa<expression>
+that are supported, and limitations on the supported combinations of
+restrictions. The consequences of violating such limitations are
+implementation defined.
 @dinss
-@i<@s8<Implementation Advice>>@hr
-Program unit pragmas that are not library-unit pragmas, when
-supported for a generic unit, should apply to all instances of the
-generic for which there is not an overriding pragma applied directly
-to the instance.
-
-NOTE@hr
-To apply a library unit pragma to an instance, it must be specified
-for the instance. A library unit pragma in the generic unit usually
-does not apply to any instances.
+Implementations are permitted to omit restriction checks for code that is
+recognized at compile time to be unreachable and for which no code is generated.
+
+Whenever enforcement of a restriction is not required prior to
+execution, an implementation may nevertheless enforce the restriction prior to
+execution of a partition to which the restriction applies, provided
+that every execution of the partition would violate the restriction.
 
 !corrigendum A.12.01 (29)
 !AI-00026

Questions? Ask the ACAA Technical Agent