| Number | 141
|
| Category | errata
|
| Synopsis | 19.7: `line number
|
| State | lrmdraft
|
| Class | mistaken
|
| Arrival-Date | Oct 02 2002
|
| Originator | "Brad Pierce" <Brad.Pierce@synopsys.com>
|
| Release | 2001b: 19.7
|
| Environment |
|
| Description |
This is a multi-part message in MIME format. ------=_NextPart_000_0008_01C269F4.DD1DF560 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit In Syntax 19-7, the first field in the `line compiler directive is a "number", but "number" is not defined here. Although there is a "number" nonterminal in the main grammar, we shouldn't allow every kind of Verilog number in the `line compiler directive. For example, according to A.8.7, one kind of Verilog "number" is "real_number". If we want to use a nonterminal from the main grammar, then "unsigned_number" probably best reflects the original intent -- `line number "filename" level --?--> `line unsigned_number "filename" level According to to A.8.7, unsigned_number ::= decimal_digit { _ | decimal_digit } -- Brad ------=_NextPart_000_0008_01C269F4.DD1DF560 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <META http-equiv=3DContent-Type content=3D"text/html; = charset=3Diso-8859-1"> <META content=3D"MSHTML 5.50.4807.2300" name=3DGENERATOR> <SPAN class=3D247390222-01102002><FONT face=3DArial><FONT =
size=3D2>In Syntax=20 19-7, the first field in<SPAN class=3D700031016-02102002> = the `line=20 compiler directive is a "number"<SPAN class=3D700031016-02102002>,=20 but "number" is not defined here. <SPAN=20 class=3D700031016-02102002>Although t<SPAN = class=3D700031016-02102002>here is=20 a "number" nonterminal in the main grammar, we shouldn't=20 allow every kind of Verilog number<SPAN = class=3D700031016-02102002> in=20 the `line compiler directive. For example, according to = A.8.7, one=20 kind of <SPAN class=3D700031016-02102002>Verilog "number" is = "real_number".<SPAN class=3D700031016-02102002> If we want to use = a=20 nonterminal from the main grammar, then "unsigned_number" probably = best=20 reflects the original intent -- <FONT face=3DArial size=3D2><SPAN=20
class=3D247390222-01102002> <FONT face=3DArial size=3D2><SPAN=20
class=3D247390222-01102002> `line number = "filename"=20 level --?--> `line = unsigned_number=20 "filename" level <FONT face=3DArial size=3D2><SPAN=20
class=3D247390222-01102002> <FONT face=3DArial size=3D2><SPAN =
class=3D247390222-01102002>According to to=20 A.8.7, <FONT face=3DArial size=3D2><SPAN=20
class=3D247390222-01102002> <FONT face=3DArial size=3D2><SPAN=20
class=3D247390222-01102002> unsigned_number = ::=3D=20 decimal_digit { _ | decimal_digit } <FONT face=3DArial size=3D2><SPAN=20
class=3D247390222-01102002> <FONT face=3DArial size=3D2><SPAN class=3D247390222-01102002>--=20
Brad <FONT face=3DArial size=3D2><SPAN=20
class=3D247390222-01102002> <FONT face=3DArial size=3D2><SPAN=20
class=3D247390222-01102002> <FONT face=3DArial size=3D2><SPAN=20
class=3D247390222-01102002> <FONT face=3DArial size=3D2><SPAN=20
class=3D247390222-01102002> ------=_NextPart_000_0008_01C269F4.DD1DF560-- |
| Fix |
No change is needed here. The reference to "number" in the syntax description is not really a reference to the BNF rule "number". |
| Audit-Trail |
|
| Unformatted |
|
Hosted by Boyd Technology