J3/06-011r1 To: J3 From: Malcolm Cohen Subject: Editor's list of unresolved technical issues Date: 2006/09/21 A. Introduction --------------- This document lists the technical issues raised by the editor with the 007. Issues are separated into two lists; the resolved ones and the unresolved ones. When an issue is resolved, the J3 note in the 007 will be deleted and the item moved from the unresolved list to the resolved list. Issue numbers will not be reused. Note that several issues were raised with the Enhanced Modules Technical Report. Because this was not an official 007, these were given numbers in the range 5000+ so as not to conflict. These issues are also listed in this document. The one-line description is just a hint as to the issue, not a comprehensive statement of it. B. Unresolved issues -------------------- 005. Reusing STOP for error termination (as well as normal termination). Feature: Co-arrays. Modified by: 06-235r1. 006. How soon termination happens. Feature: Co-arrays. Modified by: 06-235r1. 010. Inconsistent saving of allocatable co-arrays. Feature: Co-arrays. Modified by: 06-238r1. 011. CONTIGUOUS definition list not ISO conformant. Feature: Contiguous. 016. Bits compatibility term vs. "type and kind compatible". Feature: Bits. 020. "Z[P] = Z" and allocatable components. Feature: Co-arrays. 023. Intrinsic assignment, co-indexed objects, allocatable components. Feature: Co-arrays. 033. Exit code recommendations incomplete. Feature: STOP exit code. 034. Remote access to non-coarray TARGETs. Feature: Co-arrays. 039. Global scope of external units. Feature: Co-arrays. Modified by: 06-251. 040. INQUIRE(TEAM=) missing. Feature: Co-arrays. 042. Which i/o statements are allowed on preconnected units? Feature: Co-arrays. 043. Description of INPUT_UNIT requirements. Feature: Co-arrays. 044. NEXTREC= and TEAM=. Feature: Co-arrays. 049. Explicit interface for call with co-indexed object is unwarranted. Feature: Co-arrays. 050. Lack of co-indexed object argument passing considered harmful. Feature: Co-arrays. 051. Note about making copies seems unlikely to be true. Feature: Co-arrays. 054. What can be passed to a dummy co-array. Feature: Co-arrays. 055. ASYNCHRONOUS dummies and co-indexed actuals. Feature: Co-arrays. 061. COMPLEX(KIND(0d0)), BIT_SIZE, NUMERIC_STORAGE_SIZE. Feature: Bits. Modified by: 06-223 rejection. 063. Synchronisation, FORM_TEAM, SYNC_IMAGES. Feature: Co-arrays. 064. Padding value in EOSHIFT for type bits? Feature: Co-arrays. 073. IMAGE_TEAM limitations. Feature: Co-arrays. Modified by: 06-270r2. 075. Ordering sentence is too subtle. Feature: Bits. Modified by: 06-231r1. 076. Definition status and bits. Feature: Bits. Modified by: 06-232r3. 077. Extending storage association. Feature: Bits. Modified by: 06-233r1. 079. Non-aliasing rules and images. Feature: Co-arrays. 080. New features list in intro. Feature: all. Added by: 06-274r2. 081. MOLD= questions. Feature: MOLD=. Added by: 06-274r2. 082. Auto-targetting and annex C. Feature: auto-targetting. Added by: 178-mjc-001. 083. ENTRY restrictions and construct entities. Feature: BLOCK construct. Added by 178-mjc-001. 084. BLOCK constructs and USE association. Feature: BLOCK construct. Added by: 06-254r1. 085. Image number ordering in FORM_TEAM and SYNC IMAGES. Feature: Co-arrays. Added by: 06-252r2. 086. Error handling in SYNC TEAM. Feature: Co-arrays. Added by: 06-252r2. 087. There is no need for NULL_IMAGE_TEAM. Feature: Co-arrays. Added by: 06-252r2. 088. CLOSE and collectivity. Feature: Co-arrays. Added by: 06-252r2. 089. Do not add uncheckable requirements on types. Feature: Co-arrays. Added by: 06-270r2. 090. What kind of type is IMAGE_TEAM. Feature: Co-arrays. Added by: 178-mjc-001. 091. Contradiction in asynchronous input/output. Feature: Fortran 2003 base language. Added by: 178-mjc-001 (06-199). 092. Contradiction in RRSPACING. Feature: Fortran 2003 base language. Added by: 178-mjc-001. 093. SET_EXPONENT is broken for INF and NaN. Feature: Fortran 2003 base language. Added by: 178-mjc-001. 094. Constraints are inconsistent. Feature: Fortran 2003 base language. Added by: 178-mjc-001. 095. Executable statements definition now incorrect. Feature: BLOCK construct. Added by: 178-mjc-001. 5001. Referencing a submodule. Feature: Submodules. 5003. Module procedure interface block glossary entry. Feature: Submodules. C. Resolved issues ------------------ 001. Co-array Fortran model (program includes all the images?). Feature: Co-arrays. Resolved by: 06-235r1. 002. Which parts of execution are shared vs. replicated. Feature: Co-arrays. Resolved by: 06-235r1. 003. Normal termination of execution of program vs. images. Feature: Co-arrays. Resolved by: 06-236. 004. Termination warnings and messages. Feature: Co-arrays. Resolved by: 06-236. 007. The term "co-dimension" is not defined. Feature: Co-arrays. Resolved by: 06-237. 008. Bad placement/wording about automatic co-arrays not being allowed. Feature: Co-arrays. Resolved by: 06-238r1 and 178-mjc-001. 009. Allocatable co-arrays and recursion. Feature: Co-arrays. Resolved by: 06-238r1. 012. Co-array bounds description bad. Feature: Co-arrays. Resolved by: 06-239 and 06-240. 013. Co-array bounds syntax/semantics disconnect. Feature: Co-arrays. Resolved by: 06-240. 014. Bits compatibility placement. Feature: Bits. Resolved by: 06-213. 015. Bits compatibility definition: symmetry, safety. Feature: Bits. Resolved by: 06-213. 017. Bits compatibility and generic resolution. Feature: Bits. Resolved by: 06-221r1. 018. Bits kind type parameter and future extensibility. Feature: Bits. Resolved by: meeting 177 discussion. 019. Bits "semi-polymorphism" and (lack of) explicit interface requirement. Feature: Bits. Resolved by: 06-217. 021. Inadequate specification of co-subscript mapping. Feature: Co-arrays. Resolved by: 06-242. 022. Allocation of types with co-array (ultimate) components. Feature: Co-arrays. Resolved by: 06-243. 024. Intrinsic assignment, co-indexed objects, polymorphism. Feature: Co-arrays. Resolved by: 06-244. 025. Definition of "iteration". Feature: DO CONCURRENT. Resolved by: 06-195. 026. END PROGRAM effect should not be described under STOP. Feature: Co-arrays. Resolved by: 06-245r1. 027. SYNC_ALL and STOP ambiguities. Feature: Co-arrays. Resolved by: 06-245r1. 028. "Made available" is confusing and possibly meaningless. Feature: Co-arrays. Resolved by: 06-245r1. 029. Sequencing of STOP effects not after SYNC_ALL. Feature: Co-arrays. Resolved by: 06-245r1. 030. Image 1 special casing justification lack of. Feature: Co-arrays. Resolved by: 06-245r1. 031. Which images include the effect of executing C "exit"? Feature: Co-arrays. Resolved by: 06-245r1. 032. Inconsistency of exception warnings on normal termination. Feature: Co-arrays (or F2003). Resolved by: 06-245r1. 035. "team" definition. Feature: Co-arrays. Resolved by 06-247r1. 036. Image set non-coindexed requirement ineffective. Feature: Co-arrays. Resolved by: 06-248. 037. Advertisements do not belong in the standard. Feature: Co-arrays. Resolved by: 06-198. 038. Inconsistent effects of omitting STAT=. Feature: Co-arrays. Resolved by: 06-250. 041. OPEN (TEAM=) connection. Feature: Co-arrays. Resolved by: 06-257 and 178-mjc-001. 045. Input editing, list item definition, as if ineffective. Feature: Bits. Resolved by: 06-219r2. 046. Reading unsigned integers. Feature: Bits. Resolved by: 06-219r2. 047. Corresponding integers to BITS(7) might not exist. Feature: Bits. Resolved by: 06-219r2. 048. How to write list-directed bits values. Feature: Bits. Resolved by: 06-220r2. 052. Unsafe argument association for pointers. Feature: Bits. Resolved by: 06-221r1. 053. Unsafe argument association for allocatables. Feature: Bits. Resolved by: 06-221r1. 056. Collective subroutine definition. Feature: Co-arrays. Resolved by: 06-261. 057. Implicit team synchronisation not defined. Feature: Co-arrays. Resolved by: 06-262r1. 058. Tutorial information does not belong in this subclause. Feature: Co-arrays. Resolved by: 06-264r1. 059. The two different uses of THIS_IMAGE are completely different. Feature: Co-arrays. Resolved by: 06-265r1. 060. Kind of bits kind type parameter, or spurious KIND= in BITS_KIND. Feature: Bits. Resolved by: 06-222r1. 062. Another useless KIND= argument. Feature: Bits. Resolved by: 06-222r1. 065. Another useless KIND= argument. Feature: Bits. Resolved by: 06-222r1. 066. LOGICAL(bits) might not be a value. Feature: Bits. Resolved by: 06-225. 067. MERGE_BITS inconsistent with IAND et al. Feature: Bits. Resolved by: 06-226r1. 068. MERGE_BITS internal inconsistency. Feature: Bits. Resolved by: 06-226r1. 069. Extra examples need rewording, belong in annex C. Feature: Co-arrays. Resolved by: 06-267. 070. Description does not make sense for bits. Feature: Bits. Resolved by: 06-227. 071. Arithmetic shift isn't (except on 2s complement). Feature: Bits. Resolved by: 06-228. 072. Bit model does not interpret values with the top bit set. Feature: Bits. Resolved by: 06-228. 074. C names unnecessary, misleading, inhibit future and vendor extension. Feature: Bits. Resolved by: 06-230r1. 078. Images and scoping. Feature: Co-arrays. Resolved by: 06-271. 5000. Phrase "its descendant submodules". Resolved in 06-007 by 06-185. 5002. Module procedure interface body definition. Resolved in 06-007 by 06-185. 5004. Host scoping for submodules. Resolved in 06-007 by 06-185. ===END OF DOCUMENT===