Re: [sv-bc] $bits question

One possible approach to this would be to change Syntax 22-3 FROM

size_function ::=
	$bits(expression) |
	$bits(data_type)

TO

size_function ::=
	$bits(expression) |
	$bits(type_identifier) |
	$bits(integer_atom_type)


This includes both user-defined type names and the built-in ones.
It makes clear that a type identifier is legal, rather than
relying on a more obscure semantic rule off to the side.  We could
include the integer_vector_type keywords too, but those will always
produce a result of 1, so there isn't much point.

Allowing the integer_atom_type makes this less clean syntactically,
but I think users would expect them to be allowed.

Steven Sharp
sharp@cadence.com