In reply to dave_59:
In reply to VE:
As the LRMs says, the parent thread has to block or terminate before the fork/join_none process. Since each component’s run_phase is started as a separate thread, this fork/join_none gets scheduled upon returning from the task vsock_alarm_center::run_phase. But there may be other component run_phases ahead in the queue to execute before getting to the fork thread.
Thanks Dave. Would you elaborate " As the LRMs says, the parent thread has to block or terminate before the fork/join_none process."? On IEEE1800-2012, P175. it says :
join_none :: The parent process continues to execute concurrently with all the processes spawned by the fork. The spawned processes do not start executing until the parent thread executes a blocking statement or terminates.
Just want to make sure i understand it correctly.
Thanks