mirror of
https://github.com/codingo/Interlace.git
synced 2025-12-17 06:44:23 +01:00
Update README.md
This commit is contained in:
@@ -79,7 +79,9 @@ The following variables will be replaced in commands at runtime:
|
|||||||
| \_random\_ | Replaced with the randomly-chosen file from interlace |
|
| \_random\_ | Replaced with the randomly-chosen file from interlace |
|
||||||
|
|
||||||
# Advanced Command File Usage (block and blocker)
|
# Advanced Command File Usage (block and blocker)
|
||||||
Interlace also makes the use of two additional features for controlling execution flow within a command file: `\_blocker\_` and `\_block:<name>\_`.
|
Interlace also makes the use of two additional features for controlling execution flow within a command file: `_blocker_` and `_block:<name>_`. Blockers prevent execution before them, and blocks can be used to force sequential execution of threads for a target.
|
||||||
|
|
||||||
|
Threads will still multithread per-target, but using these features can allow you to control the execution flow for those targets more directly to prevent commands from running out of order.
|
||||||
|
|
||||||
## Blocker
|
## Blocker
|
||||||
Blockers prevent anything below them from executing until all commands above them have completed (for the currently active host). For example, in the following:
|
Blockers prevent anything below them from executing until all commands above them have completed (for the currently active host). For example, in the following:
|
||||||
|
|||||||
Reference in New Issue
Block a user