Re: [sv-bc] Is an unnamed block with declarations a scope?

Michael McNamara wrote:
> A task call creates a scope in the region within which it is called, and in1364 you can refer to the variables of that task call (most usefully by examining the values in a waveform display).

Thanks, I had missed your point the first time around.

The handling of hierarchical_task_identifier AND
hierarchical_block_identifier are both impacted by the choice
of whether unnamed blocks are "real scopes" (2) or "protection
brackets" ;-) (3).

For synthesis, I believe the only impact is in deciding
how to look up these hierarchical identifiers when they
are used by the disable statement.  Disables from outside
the task or block are rare in synthesis, If an unnamed
block intervened, I can't say whether the loss would be
noticeable.

To be fair and balanced: the following P1800 text supports (1)
and needs changing if either (2) or (3) is to be adopted:

19.13 [Name spaces]:
> 6) The block name space is introduced by named or unnamed blocks,
> the specify, function, and task constructs. It unifies the
> definitions of the named blocks, functions, tasks, parameters,
> named events, variable type of declaration and user-defined
> types within the enclosing construct.