| Add Proposal | Add Analysis | Edit Class, Environment, or Release |
| Number | 612
|
| Notify-List |
|
| Category | errata
|
| Synopsis | redundancies in the BNF
|
| State | open
|
| Class | errata-simple
|
| Arrival-Date | Jul 30 2004
|
| Originator | Eric Mahurin
|
| Release |
|
| Environment |
|
| Description |
There are few simple redundancies in the BNF that are there likely because there was an attempt to capture some semantics instead of just syntax. Below are the ones I found (I may have forgot to note others): module_instance (A.4.1): making module_port_connections is redundant because an ordered_port_connection can be null. procedural_continuous_assignments (A.6.2): net_assignment is a subset of variable_assignment and net_lvalue is a subset of variable_lvalue disable_statement (A.6.5): hierarchical_task_identifier and hierarchical_block_identifier are the same (hierarchical_identifier) conditional_statement (A.6.6): if_else_if_statement is redundant because the else statement can be an "if" statment which give you the same syntax and meaning. |
| Fix |
Unknown |
| Audit-Trail |
From: "Brad Pierce" <Brad.Pierce@synopsys.com> To: <etf-bugs@boyd.com> Cc: Subject: Re: errata/612: redundancies in the BNF Date: Fri, 30 Jul 2004 12:34:32 -0700 The if_else_if problem was discussed in issue 178. The minutes don't record why that issue was closed http://boydtechinc.com/etf/archive/att-0725/01-2002_12_16.txt but according to the minutes I am the culprit that moved to close it. The nonterminal clearly is redundant. -- Brad From: Shalom.Bresticker@freescale.com To: Brad Pierce <Brad.Pierce@synopsys.com> Cc: etf-bugs@boyd.com Subject: Re: errata/612: redundancies in the BNF Date: Sat, 31 Jul 2004 23:23:27 +0300 (IDT) It was closed because the ETF felt that the redundancy added some clarity to the description of the syntax, and also that it was not worth the time and effort to make the relevant changes to the text of the LRM, especially because there is no error or ambiguity in the current BNF (you get to the same end result no matter how you parse it). Shalom On Fri, 30 Jul 2004, Brad Pierce wrote: > The if_else_if problem was discussed in issue 178. > > The minutes don't record why that issue was closed > > http://boydtechinc.com/etf/archive/att-0725/01-2002_12_16.txt > > but according to the minutes I am the culprit that > moved to close it. The nonterminal clearly is redundant. |
| Unformatted |
|
Hosted by Boyd Technology