6.3 -- "Nets cannot be written by procedural statements. ... A net cannot be procedurally assigned." Is there a difference between these two? 6.3 -- "Variables can be written by one continuous assignment or one port." I guess this means by an output port, but isn't that necessarily a continuous assignment? What's the need for adding "or one port"? 6.5 -- "The keywords logic and reg are equivalent types (see 6.20.2 for details on type equivalence)." A keyword is not a type. I think that the 'logic' and 'reg' data types are at least matching, not merely equivalent, and are perhaps even identical types. I see no details about this issue in the cross-referenced 6.20.2. 6.6 -- "the variables reg, logic and bit" aren't variables 6.6 -- "data objects ... is known" 6.6.1 -- "multibit net or reg, logic or bit vector" This is mixing the concept of kind (e.g., 'net') with the concept of data type (e.g., 'logic'). 6.6.1 -- "specified by the lsb" Unnecessary italics. 6.6.1 -- "Vector nets and vectors of reg, logic and bit types shall be treated as unsigned quantities, unless declared to be signed or is connected to a port that is declared to be signed (see 22.8.3)." Again there's a mixing of kind and type. The type of a net could be logic vector. Also, how does connecting a vector to a signed port cause it to be treated as a signed quantity? There's no example using a port connection in the examples that immediately follow. And there's nothing about this in the cross-referenced section, which regards parameter value assignments. 6.9 -- The Note after Table 6-8 is unnecessary. 6.10 -- "These three types are collectively referred to as real variables." Types are referred to as variables? 6.13 -- "A class variable is a dynamic data type" A variable is a type? 6.18 and 6.18.5, "local constant"? Maybe it's OK, but worth having a discussion about this newly added terminology, that is used only twice in the draft LRM. 6.18.3.1 -- "Unlike non local parameters" --> "Unlike nonlocal parameters" 6.19 -- "The default lifetime is static." Not in classes, according to a subsequent paragraph in the same subclause. 6.20.2 -- The Note is only a note, because there is already normative text saying "If all data types within a packed structure are 2-state, the structure as a whole is treated as a 2-state vector. If any data type within a packed structure is 4-state, the structure as a whole is treated as a 4-state vector. If there are also 2-state members in the structure, there is an implicit conversion from 4-state to 2-state when reading those members and from 2-state to 4-state when writing them." -- Brad -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.Received on Thu Apr 5 12:41:58 2007
This archive was generated by hypermail 2.1.8 : Thu Apr 05 2007 - 12:42:42 PDT