Re: [sv-bc] variable declaration assignments

Field "variables" of a union cannot be initialized.  Although a rule
that might make sense would say "at most one" of them may be given a
default initializer.

Bresticker, Shalom wrote:
> Hi,
> 
> Mantis 1555 is for clarification is that an initializer can appear in a
> variable declaration not only in a module/program/interface, but also in
> subroutines, procedural blocks, and $unit.
> 
> 6.7 says simply,
> "A variable can be declared with an initializer, for example:***** int*
> i = 0;"
> 
> There has sometimes been confusion about this, so it would be good to
> clarify it more explicitly.
> 
> My question is, what exceptions are there?
> 
> I thought of udp_reg_declaration. What else?
> 
> It would seem not to make sense for a module/interface/program input
> port variable declaration. There is an enhancement request to allow them
> as default connection values.
> 
> Till now, subroutine output port declarations did not allow them and
> even the Mantis 1602 proposal would define them as default bindings, not
> as initializers.
> 
> assertion_variable_declaration does not seem to allow initializers as well.
> 
> Perhaps it would nevertheless be better to state where initializers are
> allowed rather than the exceptions.
> 
> Thanks,
> Shalom
> 
> 
> Shalom Bresticker
> Intel Jerusalem LAD DA
> +972 2 589-6852
> +972 54 721-1033
> 
> 
> -- 
> This message has been scanned for viruses and
> dangerous content by *MailScanner* <http://www.mailscanner.info/>, and is
> believed to be clean.


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