[sv-bc] Mantis 1610: Scoping of unnamed sequential blocks

Hi,

Mantis 1610 passed in the email vote, but there were two comments that
we did not discuss in the last meeting.

Brad wrote, "A type declared even in a named block can't be
hierarchichally referenced, can it? The text doesn't say it can, but I
can imagine someone making that inference." 

That was in reference to the text in the proposal, "An unnamed block
creates a new hierarchy scope only if it directly contains a block item
declaration, such as a variable declaration or a type declaration. This
hierarchy scope is unnamed and the items declared in it cannot be
hierarchically referenced (see 6.21)."

That first sentence, "An unnamed block creates a new hierarchy scope
only if it directly contains a block item declaration, such as a
variable declaration or a type declaration," was based in a similar
sentence in the SV-CC Mantis 1741, which had a similar topic, and was
itself based on a comment there from Steven, "Francoise is right that a
local type declaration should also make the unnamed block be a scope.
The proposal should be amended to include that."

Any comments?

Also, Steven wrote, "Shouldn't we try to provide a standard
compiler-generated naming convention for unnamed blocks? I would suggest
following the pattern used for generate blocks, but with "genblk"
replaced with something like "unmblk"." I have filed that as an
enhancement request in Mantis 2167.

Shalom

Shalom Bresticker
Intel Jerusalem LAD DA
+972 2 589-6852
+972 54 721-1033

---------------------------------------------------------------------
Intel Israel (74) Limited

This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.