J3/17-125 To: J3 From: John Reid & Bill Long Subject: Team number for initial team Date: 2017 February 09 Discussion ---------- If TEAM_NUMBER is invoked for the initial team, the value returned is -1, which is not valid as a team number in an image selector or an invocation of IMAGE_INDEX or NUM_IMAGES. These inconsistencies disappear if the value 1 is returned by TEAM_NUMBER instead of -1. We allow a CHANGE TEAM construct to keep all the images of the current team in the new team and in this case they all have the same team number. For consistency, we should treat the initial team similarly. While working on the edits, we noticed that in 5.3.4 the initial team is not defined as the team existing at the beginning of program execution, although it is so defined in the terms section. We have corrected this. Edits to 17-007 --------------- [22:36] In 3.145.4 definition of the term "team number", replace the definition with "integer value that identifies a team within its parent team, or the value 1 if there is no parent team". [40:21] In 5.3.4 Program execution, para 2, sentence 1, before "consisting" insert "the team team existing at the beginning of program execution and". [40:24] In 5.3.4 Program execution, at the end of para 2, insert the new sentence "The team number for the initial team is 1." [140:2] In 9.6 Image selectors, para 3, final sentence, after "Otherwise," add "the value of the shall be 1 and". [394:11] In 16.9.97 IMAGE_INDEX (COARRAY, SUB) ..., para 3, TEAM_NUMBER, change "If the current team is not the initial team" to "If the current team is the initial team, it shall have the value 1; otherwise". [415:26] In 16.9.145 NUM_IMAGES ( ) ..., para 3, TEAM_NUMBER, change "If the current team is not the initial team" to "If the current team is the initial team, it shall have the value 1; otherwise". [434:24] In 16.9.189 TEAM_NUMBER([TEAM]), para 5, Result Value, change "-1" to "1".