On second thoughts, it should be disabled because of section 3.14.2.2 since the checker is embedded inside a module or interface. The illegal use of timeunit and timeprecision in a checker is implicitly defined, but not explicit. 3.14.2.2 The timeunit and timeprecision keywords There shall be *at most one time unit and one time precision for any module, program, package, or interface **definition* or in any compilation-unit scope. This shall define a time scope. If specified, the timeunit and timeprecision declarations shall precede any other items in the current time scope. The timeunit and timeprecision declarations can be repeated as later items, but must match the previous declaration within the current time scope On Thu, Jan 29, 2015 at 1:34 PM, Ben Cohen <hdlcohen@gmail.com> wrote: > I could not find this restriction in 1800. > If it is (or is not) shouldn't this be addressed? > Ben > -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.Received on Thu Jan 29 13:50:01 2015
This archive was generated by hypermail 2.1.8 : Thu Jan 29 2015 - 13:50:05 PST