# Checking clock period using system verilog assertion

**URL:** <https://verificationacademy.com/forums/t/checking-clock-period-using-system-verilog-assertion/30272>\
**Category:** SystemVerilog\
**Tags:** SystemVerilog, assertion\
**Created:** [January 7, 2015, 12:30pm UTC](https://verificationacademy.com/forums/t/checking-clock-period-using-system-verilog-assertion/30272 "2015-01-07T12:30:57Z")\
**Posts on this page:** 1\
**Showing post:** 20

<div class="post-metadata">

**Author:** ![silverace99](https://verificationacademy.com/forums/letter_avatar_proxy/v4/letter/s/ccd318/32.png) [@silverace99](https://verificationacademy.com/forums/u/silverace99)\
**Post date:** [August 11, 2017, 4:58pm UTC](https://verificationacademy.com/forums/t/checking-clock-period-using-system-verilog-assertion/30272/20 "2017-08-11T16:58:10Z")

</div>

_In reply to [ben@SystemVerilog.us](https://verificationacademy.com/forums/t/checking-clock-period-using-system-verilog-assertion/30272/19):_

I see. so by pulling all the variables into a function, you’ve moved the variable scope up to a level an error message can access. Very cool. Thanks Ben!

---

_[View the full topic](https://verificationacademy.com/forums/t/checking-clock-period-using-system-verilog-assertion/30272)._
