Date: Wed Apr 11 2007 - 06:25:49 PDT
Hi, Stu inserted a number of questions to the committees in the margins of the draft merged LRM. I've made a list of them. I have my own answers to some of them, but that is for a separate mail. 4.8.5: Do clocking block assignment scheduling semantics need to be added? 5.7, Table 5-2: Should "step" be added to this table? (per A.8.4) 7.1.1: Are there any data type restrictions for unpacked structures (e.g. dynamic types)? 10.5.1: Does the result of a continuous assign to a variable update immediately when the variable is released? 10.5.1: What about unpacked stucts, enums, classes, etc.? 10.5.2: What about unpacked stucts, enums, classes, etc. 11.1.1: Are all operators listed in table 11-1 after merging in SV still legal in constant expressions? 11.2.18: Is the shorter operand always zero extended, or can it be sign extended? 11.3.2: This text comes directly from 1364-2005. There was no matching subclause from 1800-2005 to merge in. Is new text needed for SV array addressing ? 13.1: Is it still true that a function must have at least one input? 13.3: Is this 1364 restriction still true? 13.3.4: Also interface and program? 20.1.1: Is string type added correctly? 20.1.3: Is string type added correctly? 20.1.4.3: Is string type added correctly? 20.1.7: Is string type added correctly? 20.4: Is string type added correctly? 21.3: What is this "unchanged behavior"? I could not find it in 1364. 22.2.1: Is this last sentence still true in SV? 22.2.3.3: Is 'z correct for all net types (e.g. tri1)? 24.8: Does this new example need an intro paragraph or follow-on explanation? Shalom Bresticker Intel Jerusalem LAD DA +972 2 589-6852 +972 54 721-1033 -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.
