| Number | 250
|
| Category | errata
|
| Synopsis | A.8.3: Is expression redundant in range_expression?
|
| State | closed
|
| Class | errata-simple
|
| Arrival-Date | Jan 06 2003
|
| Originator | Dan.Jacobi@intel.com
|
| Release | 2001b: A.8.3
|
| Environment |
#123 SV-BC19-45, 47 |
| Description |
From Dan Jacobi in SV-BC19-45 and 47: In A.8.3, constant_range_expression ::= constant_expression | msb_constant_expression : lsb_constant_expression | constant_base_expression +: width_constant_expression | constant_base_expression -: width_constant_expression constant_range_expression is used only in net_lvalue. After the fix of #53, net_lvalue ::= hierarchical_net_identifier {[constant_expression]}[[constant_range_expression]] | {net_lvalue {, net_lvalue}} Thus, it seems that constant_expression is redundant in constant_range_expression as net_value already contains the constant_expression possiblity even without constant_range_expression. Similarly, expression (or constant_expression, see issue #238) is already used everywhere that range_expression is used, so expression appears redundant in the definition of range_expression. See also issue #123. |
| Fix |
Closed because of ETF-passed issue 238, constant_expression can no longer be removed from constant_range_expression. And if we're not changing constant_range_expression, we shouldn't change range_expression either. |
| Audit-Trail |
|
| Unformatted |
|
Hosted by Boyd Technology