Compiladores

The scope of each defining-point shall be its region (including all regions enclosed by that region)
subject to 6 .2 .2 .5 and 6 .2 .2 .6.
6.2 .2 .5
When an identifier or label has adefining-point for region A and another identifier or label having
the same spelling has a defining-point for some region B enclosed by A, then region B and all regions
enclosed by B shall be excluded from thescope of the defining-point for region A.
6.2 .2 .6
The region that is the field-specifier of a field-designator shall be excluded from the enclosing scopes.
6.2 .2 .7
When an identifier or labelhas a defining-point for a region, another identifier or label with the
same spelling shall not have a defining-point for that region.
6.2 .2 .8
Within the scope of a defining-point of an identifieror label, each occurrence of an identifier or label
having the same spelling as the identifier or label of the defining-point shall be designated an applied
occurrence of the identifier or label ofthe defining-point, except for an occurrence that constituted
the defining-point ; such an occurrence shall be designated a defining occurrence. No occurrence
outside that scope shall be an appliedoccurrence.
NOTE | Within the scope of a defining-point of an identifier or label, there are no applied occurrences of
an identifier or label that cannot be distinguished from it and have adefining-point for a region enclosing
that scope.
6.2 .2 .9
The defining-point of an identifier or label shall precede all applied occurrences of that identifier
or label contained by the program-blockwith one exception, namely that an identifier can have an
applied occurrence in the type-identifier of the domain-type of any new-pointer-types contained by
the type-definition-part containing thedefining-point of the type-identifier.
6.2 .2.10
Required identifiers that denote required values, types, procedures, and functions shall be used as if
their defining-points have a region enclosing...