(j3.2006) Public Comment J32034

[Jim Giles]

Van Snyder wrote:
> It's interesting that Jim finds
> 
>  CRITICAL
>    BLOCK
>      ...
>    END BLOCK
>  END CRITICAL
> 
> and
> 
>  CRITICAL
>    <specification-part>
>    <execution-part>
>  END CRITICAL
> 
> unacceptable, but
> 
>  ASSOCIATE ...
>    BLOCK
>      ...
>    END BLOCK
>  END ASSOCIATE
> 
> should be the only allowed way to accomplish the obvious things it
> does. 

ASSOCIATE isn't a new consruct, so I didn't comment on it at all.
Actually I find it appalling.

I've always thought that host association should not be automatic,
but should be controlled.  Anything you don't explicitly import
should not be visible in the nested scoping unit.  That should 
apply to all forms of host association: BLOCKs, internal procedures,
and module procedures.  The rename list on whatever statement
imports from the host should be allowed the kinds of associations
that ASSOCIATE does.

J. Giles