| Add Proposal | Add Analysis | Edit Class, Environment, or Release |
| Number | 598
|
| Notify-List |
|
| Category | errata
|
| Synopsis | "$" ambiguity in PATHPULSE$
|
| State | open
|
| Class | errata-discuss
|
| Arrival-Date | Jul 19 2004
|
| Originator | Eric Mahurin
|
| Release |
|
| Environment |
|
| Description |
One of the pulse_control_specparam alternatives starts with this: PATHPULSE$specify_input_terminal_descriptor$specify_output_terminal_descriptor But, these two terminal descriptors can be simple identifiers which also allow "$". No spaces are allowed between the "$"s above, right? Should these terminal descriptors only allow simple identifiers that don't have "$"? Who came up with this crazy syntax? |
| Fix |
Unknown |
| Audit-Trail |
From: Shalom.Bresticker@freescale.com To: eric_mahurin@yahoo.com Cc: etf-bugs@boyd.com Subject: Re: errata/598: "$" ambiguity in PATHPULSE$ Date: Wed, 21 Jul 2004 13:11:21 +0300 (IDT) Strictly speaking, according to the BNF, I think the terminal descriptors could even be escaped identifiers, but probably no one actually allows that. As for history, this is legacy from Verilog-XL. Shalom > One of the pulse_control_specparam alternatives starts with this: > > PATHPULSE$specify_input_terminal_descriptor$specify_output_terminal_descriptor > > But, these two terminal descriptors can be simple identifiers which also allow "$". No spaces are allowed between the "$"s above, right? Should these terminal descriptors only allow simple identifiers that don't have "$"? > > Who came up with this crazy syntax? -- Shalom Bresticker Shalom.Bresticker @freescale.com Design & Reuse Methodology Tel: +972 9 9522268 Freescale Semiconductor Israel, Ltd. Fax: +972 9 9522890 POB 2208, Herzlia 46120, ISRAEL Cell: +972 50 5441478 |
| Unformatted |
|
Hosted by Boyd Technology