| Number | 195
|
| Category | errata
|
| Synopsis | 3.11.3: last example has syntax errors
|
| State | lrmdraft
|
| Class | errata-simple
|
| Arrival-Date | Nov 18 2002
|
| Originator | "Brad Pierce" <Brad.Pierce@synopsys.com>
|
| Release | 2001b: 3.11.3
|
| Environment |
|
| Description |
In the final example, there is a missing semicolon in the first line and the port directions are not declared. Proposal -- module RAM16GEN (DOUT, DIN, ADR, WE, CE) ---> module RAM16GEN (output DOUT, input DIN, ADR, WE, CE) ; -- Brad |
| Fix |
REPLACE: module RAM16GEN (DOUT, DIN, ADR, WE, CE) WITH: module RAM16GEN (output [7:0] DOUT, input [7:0] DIN, input [5:0] ADR, input WE, CE) ; |
| Audit-Trail |
From: Charles Dawson <chas@cadence.com> To: ETF <etf-bugs@boyd.com> Cc: Subject: errata/195: whitespace issue Date: Mon, 12 Jan 2004 11:56:53 -0500 We think the solution for this issue is to include nulls in the white-space characters specification in 17.2.4.3 (a) (as previously suggested by Gord). Specifically, the text should read: a) White-space characters (blanks, tabs, new-lines, or form-feeds) that, except in one case described below, cause input to be read up to the next non-white-space character. For $sscanf, null characters shall also be considered white-space. Note that this change also effects null characters that are embedded within the string. I should have an example to illustrate this shortly. -Chas |
| Unformatted |
|
Hosted by Boyd Technology