| Add Proposal | Add Analysis | Edit Class, Environment, or Release |
| Number | 424
|
| Category | errata
|
| Synopsis | Clarify terms "design unit", "description" and "hardware description"
|
| State | open
|
| Class | errata-simple
|
| Arrival-Date | Aug 21 2003
|
| Originator | Jay Lawrence - Cadence Design Systems
|
| Release | 2001b
|
| Environment |
|
| Description |
In section 13.2, the following sentence occurs: "The text macro names are defined in the linear order of appearance in the set of input files that make up the description of the design unit." The term design unit is never defined anywhere however (at least not be searching the pdf file. In general the LRM often says things like "module, macromodule, and primitive". It would be advantageous to define a single term that refers to all forms of top-level descriptions. The term description is used, but only inconsistently. Some times it is a general noun (e.g. a waveform description), sometimes it refers to an elaborated hierarchy, and sometimes it refers to a single uninstantiated module, macromodule or primitive. I believe we should define term "design unit" to be module, macromodule, config, or UDP. Any other kinds of top-level units (packages, program blocks, ...) would be added to this definition as needed. A thorough search of the LRM for "description" with appropriate replacement will be necessary. |
| Fix |
|
| Audit-Trail |
|
| Unformatted |
|
Hosted by Boyd Technology