Hello,
LRM sections 9.2 and 9.3 describe always_comb and always_latch.
It is stated that both constructs automatically determine their sensitivity.
The examples show no sensitivity lists.
However, the BNF groups all forms of always block together.
Thus, syntactically it is legal to create an always_comb or always_latch
process with a sensitivity list.
Do we want that?
I think we need to do one of three things:
1. Modify the BNF to make it illegal to add a sensitivity list after
always_comb or always_latch.
2. Declare that such a sensitivity list is illegal in the normative
sections.
3. Explain what the semantics of such a list are, if it is legal. (ignored?)
Thanks and regards,
Doug
Received on Thu Aug 5 13:43:33 2004
This archive was generated by hypermail 2.1.8 : Thu Aug 05 2004 - 13:44:55 PDT