# Declaring timeunit in package

**URL:** <https://verificationacademy.com/forums/t/declaring-timeunit-in-package/29760>\
**Category:** SystemVerilog\
**Tags:** import, SystemVerilog, Package, timeunit\
**Created:** [July 31, 2014, 12:30pm UTC](https://verificationacademy.com/forums/t/declaring-timeunit-in-package/29760 "2014-07-31T12:30:50Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![dave\_59](https://verificationacademy.com/forums/user_avatar/verificationacademy.com/dave_59/32/4499_2.png) [@dave\_59](https://verificationacademy.com/forums/u/dave_59)\
**Post date:** [August 9, 2014, 5:57am UTC](https://verificationacademy.com/forums/t/declaring-timeunit-in-package/29760/4 "2014-08-09T05:57:13Z")

</div>

_In reply to [ben@SystemVerilog.us](https://verificationacademy.com/forums/t/declaring-timeunit-in-package/29760/3):_

Not a good idea. Period will get scaled to the local timescale. Unlike VHDL, there is no physical timescale unit information saved with the value. If the local timescale was 1ns, the Period = 1.5. When you pass Period to another scope, there will be no way to know that 1.5 is in ns.

---

_[View the full topic](https://verificationacademy.com/forums/t/declaring-timeunit-in-package/29760)._