To: J3 J3/21-011 From: Malcolm Cohen Subject: Editor's list of unresolved technical issues Date: 2020-December-18 A. Introduction --------------- This document lists the technical issues raised by the editor with the current working document, standing document 007. Issues are separated into two lists; the resolved ones and the unresolved ones. When an issue is resolved, the J3 note in SD-007 will be deleted and the item moved from the unresolved list to the resolved list. Issue numbers will not be reused. The one-line description is just a hint as to the issue, not a comprehensive statement of it. The editor notes that all Unresolved Technical Issues are indexed in the working draft 007, as ZZZUTInnn. Thus you can find them quickly by going to the last page and clicking on the index reference. B. Unresolved issues -------------------- 001. What do you mean "same set", and why does it matter? Feature: Arrays of coarrays. Added in: 20-007 as a result of processing 19-250r1. 008. Output of boz-literal-constant inconsistent and does not work for w=0. Feature: Extending use of BOZ constants. Added in: 20-007 as a result of processing 19-256r2. C. Resolved issues ------------------ 002. SEPARATOR is pointless in the FIRST+LAST form. Feature: ISO_FORTRAN_STRINGS US03. Added in: 20-007 as a result of processing 19-254r2. Resolved in 20-007r1 by 20-139. 003. BACK is useless complication in all but the POS form. Feature: ISO_FORTRAN_STRINGS US03. Added in: 20-007 as a result of processing 19-254r2. Resolved in 20-007r1 by 20-139. 004. POS form of SPLIT does not identify whole tokens. Feature: ISO_FORTRAN_STRINGS US03. Added in: 20-007 as a result of processing 19-254r2. Resolved in 20-007r1 by 20-139. 005. So what are the bounds of a pointer variable here? Feature: Reductions for DO CONCURRENT (US20). Added in: 20-007 as a result of processing 19-255r2. Resolved in 20-007r1 by 20-158r3. 006. Why does a REDUCE entity have POINTER when it must be associated and cannot be re-associated? Feature: Reductions for DO CONCURRENT (US20). Added in: 20-007 as a result of processing 19-255r2. Resolved in 20-007r1 by 20-158r3. 007. Why is the reduction variable re-initialized every iteration? Feature: Reductions for DO CONCURRENT (US20). Added in: 20-007 as a result of processing 19-255r2. Resolved in 20-007r1 by 20-160r3. 009. Output of boz-literal-constant is not permitted at all. Feature: Extending use of BOZ constants. Added in: 20-007 as a result of processing 19-256r2. Resolved in 20-007r1 by 20-156r1. 010. Why can BOZ be used to init a PARAMETER but not a variable? Feature: Extending use of BOZ constants. Added in: 20-007 as a result of processing 19-256r2. Resolved in 20-007r1 by 20-145. 011. Entire example is subsumed by new "auto-allocate intrinargs" feature. Feature: Auto-allocate characters (US14). Added in: 20-007 as a result of processing 18-267. Resolved in 20-007r1 by 20-140. 012. Is NOTIFY= meant to work only on coarrays and not pointer components thereof? Feature: Put with Notify (US13). Added in: 20-007 as a result of processing 19-259r1. Resolved in 20-007r1 by 20-146. 013. TYPEOF and CLASSOF permit invalid declarations. Feature: TYPEOF and CLASSOF" (US16/17/18/24). Added in: 20-007 as a result of processing 20-114r1. Resolved in 20-007r1 by 20-148r2. 014. TYPEOF and CLASSOF cannot be used with TYPE(*) or CLASS(*). Feature: TYPEOF and CLASSOF" (US16/17/18/24). Added in: 20-007 as a result of processing 20-114r1. Resolved in 20-007r1 by 20-148r2. 015. Fortran 202x is not upwards compatible with F2018. Feature: Auto-allocate characters (US14). Added in: 20-007 as a result of processing 20-122r1. Resolved in 20-007r1 by 20-137r1. 016. Technical changes from 20-104r3 amount to a new feature. Feature: Allegedly editorial paper made technical changes. Added in: 20-007 as a result of processing 20-104r3. Resolved in 20-007r1 by 20-163. 017. If C_CHAR==-1, do these exist? Feature: C_F_STRPOINTER and F_C_STRING (US09) Added in: 20-007 as a result of processing 19-197r3. Resolved in 20-007r1 by 20-141r1. ===END OF DOCUMENT===