|author||Joel Sherrill <joel.sherrill@OARcorp.com>||2000-05-01 20:08:58 +0000|
|committer||Joel Sherrill <joel.sherrill@OARcorp.com>||2000-05-01 20:08:58 +0000|
A bit more explanation for task variables per Eric Norum <email@example.com>.
Diffstat (limited to 'doc/user')
1 files changed, 7 insertions, 0 deletions
diff --git a/doc/user/task.t b/doc/user/task.t
index 7c57beff4a..e399f2ea74 100644
@@ -301,6 +301,13 @@ other tasks' modifications to that variable will not affect the value
seen by the task. This is accomplished by saving and restoring the
variable's value each time a task switch occurs to or from the calling task.
+The value seen by other tasks, including those which have not added the
+variable to their set and are thus accessing the variable as a common
+location shared among tasks, can not be affected by a task once it has
+added a variable to its local set. Changes made to the variable by
+other tasks will not affect the value seen by a task which has added the
+variable to its private set.
This feature can be used when a routine is to be spawned repeatedly as
several independent tasks. Although each task will have its own stack,
and thus separate stack variables, they will all share the same static and