LRM section 4.5 partly answered my question…now I think all processes proceeds and gets scheduled in parallel. If there are iterations in so-called iterative regions, process moves back and forth between active (or reactive) region and other regions.
Now I’m wondering what #n or ##n (with default clocking) would mean in scheduling semantics? Move directly to active region n-timeunit away/n-cycle away?
In reply to eda2k4: