| Number | 91
|
| Category | errata
|
| Synopsis | Note 7 in section 26.6.5 is misleading
|
| State | lrmdraft
|
| Class | errata-ptf
|
| Arrival-Date | Aug 07 2002
|
| Originator | Charles Dawson
|
| Release | 2001b: 26.6.5
|
| Environment |
|
| Description |
The note says that both vpiHighConn _and_ vpiLowConn will be NULL if the port is unconnected. This is not exactly true. If it is a NULL port (ie module M();) then the lowconn (at least) will be NULL. If the instance of M also does not connect to the port, then the highconn will be NULL as well. This is what the note was intended to convey, but it doesn't do a very good job. |
| Fix |
Section 26.6.5, change note 7 FROM: "7)vpiHighConn and vpiLowConn shall return NULL if the port is not connected." TO: "7) vpiLowConn shall return NULL if the module port is a null port (e.g. module M();). vpiHighConn shall return NULL if the instance of the module does not have a connection to the port." |
| Audit-Trail |
From: Shalom Bresticker <Shalom.Bresticker@motorola.com> To: ptf-bugs@boyd.com Cc: Subject: Re: errata/91: PROPOSAL - Note 7 in section 26.6.5 is misleading Date: Tue, 17 Jun 2003 12:45:38 +0300 Today the term "null port" is not defined. It is not even used anywhere else in the LRM except in Note 8 in this section. In "M ( a , , c )", is the middle port also a null port ? > Section 26.6.5, change note 7 > FROM: > "7)vpiHighConn and vpiLowConn shall return NULL if the port is not connected." > > TO: > "7) vpiLowConn shall be NULL if the module port is a null port (i.e.: module M();). vpiHighConn shall be NULL if the instance of the module does not have a connection to the port." > > http://boydtechinc.com/cgi-bin/issueproposal.pl?cmd=view&pr=91 Shalom |
| Unformatted |
|
Hosted by Boyd Technology