CVS difference for ai12s/ai12-0005-1.txt

Differences between 1.28 and version 1.29
Log of other versions for file ai12s/ai12-0005-1.txt

--- ai12s/ai12-0005-1.txt	2019/04/03 07:15:09	1.28
+++ ai12s/ai12-0005-1.txt	2019/06/11 04:13:53	1.29
@@ -1407,9 +1407,50 @@
 13.14(3.g/4) Ramification: Note that the rule about proper 
 bodies [being]{causing} freezing only applies in declarative_parts.
-Editor's note (April 2, 2019): All of the items above this
+From: Steve Baird
+Sent: Tuesday, May 28, 2019  5:04 PM
+[From private mail.]
+>> AFAIK, there are no restrictions on calling 
+>> Task_Identification.Current_Task during the execution of a parallel 
+>> construct.
+>> Should there be? I don't think so, but I raise the question.
+> I don't see any problem here, a task /= LToC. The id would be in the 
+> TCB somehow, and that has to be accessible from any thread executing 
+> on behalf of that task (for things like task attributes as well as the
+> task id).
+>> Do we want a C.7.1 AARM note saying something about interactions with 
+>> parallel constructs, just for clarification?
+> Doesn't seem necessary, seems obvious to me. But what would you suggest??
+> (We don't need to do anything "official" to add such a note, someone 
+> needs to author it and I can just add it.)
+If it seems obvious then I'm fine with no action.
+Would there be any value in something like
+    The logical threads of control associated with the execution
+    of a given parallel construct all execute as part of the execution of
+    one task. Thus, the result returned by a call to
+    Task_Identification.Current_Task is independent of whether the call
+    takes place during the execution of a parallel construct.
+? "No" is a fine answer.
+Editor's note (May 28, 2019): All of the items above this
 marker have been included in the working version of the AARM.

Questions? Ask the ACAA Technical Agent