# Why loop variable should not be used in FORK JOIN\_NONE

**URL:** <https://verificationacademy.com/forums/t/why-loop-variable-should-not-be-used-in-fork-join-none/39849>\
**Category:** SystemVerilog\
**Tags:** SystemVerilog\
**Created:** [November 26, 2021, 10:12am UTC](https://verificationacademy.com/forums/t/why-loop-variable-should-not-be-used-in-fork-join-none/39849 "2021-11-26T10:12:47Z")\
**Posts on this page:** 1\
**Showing post:** 6

<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:** [July 20, 2023, 5:58am UTC](https://verificationacademy.com/forums/t/why-loop-variable-should-not-be-used-in-fork-join-none/39849/6 "2023-07-20T05:58:11Z")

</div>

_In reply to [svq](https://verificationacademy.com/forums/t/why-loop-variable-should-not-be-used-in-fork-join-none/39849/5):_

This has to do with the _actual_ values passed into write\_int(). Even though each call to the task has its own copy of the formal arguments, they all will have the same value of i by the time the call occurs. It has nothing to do with the task being static or automatic in this case.

---

_[View the full topic](https://verificationacademy.com/forums/t/why-loop-variable-should-not-be-used-in-fork-join-none/39849)._