12.3 "Pessimism reduction can also be done using unique-case priority-case (see 12.3.3)." I don't understand this. Could you please provide an example of using these constructs to reduce x-pessimism? Also, the phrase "unique-case priority-case" is strange. 12.5.1 "The variable used to control a for-loop can be declared prior to the loop" Should be "variables". 12.5.1 "The variable used to control a for-loop can also be declared within the for-loop" Should be "variables" 12.7 "can have name specified" Missing "a". 13.1 "A function shall have at least one input type argument" A function needn't have any arguments. 13.1 "A function nonvoid function can be" Extra "function" 13.2.1 "Tasks defined within a module, interface, program or package default to being static, with all declared items" Not if the module, interface, program or package is declared to have an 'automatic' lifetime, as noted in the second bullet after this sentence. The default lifetime of a subroutine is the lifetime of the construct in which it is declared. 13.3 "If a packed_dimension is specified, the function shall return a packed array of type logic." The mention of the optional signing has been deleted from this paragraph. 13.3.3 "These items shall be shared across all uses of the task executing concurrently." "Functions can defined to use static storage by explicitly defining the task as static" The section is about functions, not tasks. These typos go to show that there is unnecessary repetition here. Whether a subroutine is static or automatic is orthogonal to whether it is a task or function. 13.4 "Task or function" Instead of saying "task or function", why not say "subroutine", as in 13.4.1? 13.4 "listed of the call" ?? 13.4.4 "The fun function" "fun" should be in a monospaced font. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.Received on Wed Apr 11 16:24:05 2007
This archive was generated by hypermail 2.1.8 : Wed Apr 11 2007 - 16:24:32 PDT