[sv-ac] review of 3069

Hello,

- I think that programs need not be excluded. Since there is no hierarchy under a program (except perhaps checkers) the global clock would apply only to the program and effectively be equivalent to declaring default clock. However, the distinction would be needed for library properties that reference $global_clock and are instantiated in an assertion in the program.

- I think that more examples are needed, to show the hierarchical nature of global clocking.

- Would it be useful to allow global clocking specification in configuration files, such that it would be applied after the global clocking defined in the design, overriding when conflict arises?

best regards,
ed

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.