# Fork-join\_none with delay

**URL:** <https://verificationacademy.com/forums/t/fork-join-none-with-delay/38088>\
**Category:** SystemVerilog\
**Tags:** SystemVerilog, for-loop-fork-join\_none\
**Created:** [September 17, 2020, 2:14am UTC](https://verificationacademy.com/forums/t/fork-join-none-with-delay/38088 "2020-09-17T02:14:08Z")\
**Posts on this page:** 1\
**Showing post:** 8

<div class="post-metadata">

**Author:** ![ssakshi](https://verificationacademy.com/forums/letter_avatar_proxy/v4/letter/s/3d9bf3/32.png) [@ssakshi](https://verificationacademy.com/forums/u/ssakshi)\
**Post date:** [September 17, 2020, 6:53pm UTC](https://verificationacademy.com/forums/t/fork-join-none-with-delay/38088/8 "2020-09-17T18:53:16Z")

</div>

_In reply to [dave\_59](https://verificationacademy.com/forums/t/fork-join-none-with-delay/38088/7):_  
This sounds like a silly question but I am still not able to understand if #1 delay before fork-join\_none can be treated as a blocking statement to start the execution of spawned processes, then why does display statement after fork-join\_none is executed(printed) before the display statement in fork-join\_none.  
(Why does the spawned process wait until the parent thread terminates?)

As per my understanding, fork-join\_none should start execution as soon as the parent thread executes a blocking statement (#1 before fork-join\_none).

---

_[View the full topic](https://verificationacademy.com/forums/t/fork-join-none-with-delay/38088)._
