#0 in SystemVerilog inactive event region

Dave,

Thanks for your response. I know I can count on you :)

But is #0 the whole reason for the existence of inactive region in SystemVerilog event scheduling? Also the whole purpose of active/inactive iteration? Giving execution/process a chance to go back to active region.

In this regard, would NBA be the same?

In reply to dave_59: