From jwagener@amoco.com Mon May 15 11:49:47 1995 Received: from interlock.amoco.com by dkuug.dk with SMTP id AA02735 (5.65c8/IDA-1.4.4j for ); Mon, 15 May 1995 23:51:52 +0200 Received: by interlock.amoco.com id AA16938 (InterLock SMTP Gateway 3.0 for sc22wg5@dkuug.dk); Mon, 15 May 1995 16:50:06 -0500 Message-Id: <199505152150.AA16938@interlock.amoco.com> Received: by interlock.amoco.com (Protected-side Proxy Mail Agent-3); Mon, 15 May 1995 16:50:06 -0500 Received: by interlock.amoco.com (Protected-side Proxy Mail Agent-2); Mon, 15 May 1995 16:50:06 -0500 Received: by interlock.amoco.com (Protected-side Proxy Mail Agent-1); Mon, 15 May 1995 16:50:06 -0500 From: jwagener@amoco.com X-Openmail-Hops: 1 Date: Mon, 15 May 95 16:49:47 -0500 Subject: WG5 Tokyo Resolutions and X3J3 Responses To: sc22wg5@dkuug.dk X-Charset: ASCII X-Char-Esc: 29 Item Subject: Message text To WG5 and X3J3 - This will be a bit of a test, to see if everyone can handle RTF; presumably anyone using the latest versions of Word, WordPerfect, Frame, ... can import RTF. If you can't, at least the RTF itself is somewhat readable - let me know if your word processing product can't read the second and third attachments. There are three attachments to this note: 1. the WG5 Tokyo resolutions (that David Muxworthy distributed) 2. the X3J3 responses to those resolutions (passed unanimously in Maui) 3. X3J3/95-128r1, which is a detailed response to Tokyo resolution T7 The responses do not list the individuals that X3J3 appoints to the various technical report development bodies, as the responses were approved prior to the identification of those individuals. Please add "Keith Bierman, Kurt Hirchert, ..." to the response to T8 (floating point exception handling), "Graham Barber, Linda O'Gara, Henry Zongaro, ..." to the response to T9 (interoperability with C), and "David Epstein, ..." to the response to T10 (data type enhancements ...). The reason for the "..." in each case is that there is an X3J3 subgroup that is assigned as liaison with each of the technical report development bodies. In the case of T8, that subgroup is X3J3/parallel; in the case of T9, that subgroup is X3J3/interop (a new subgroup, replacing /osci); in the case of T10, that subgroup is X3J3/oof. Jerry ....................................................................... FROM: dtm/unix_in////////HPMEXT1/dtm#a#castle#f#ed#f#ac#f#uk@houeosm4 TO: sc22wg5@dkuug.dk ....................................................................... Item Subject: (SC22WG5.799) WG5 Tokyo Resolutions Received: from hou.amoco.com (earth) by houeosm4 with SMTP (1.37.109.16/16.2) id AA086111492; Mon, 1 May 1995 07:31:32 -0500 Received: from netserv2 by hou.amoco.com (4.1/SMI-4.1) id AA03442; Mon, 1 May 95 07:31:08 CDT Errors-To: x3j3-request@newton.ncsa.uiuc.edu Received: from interlock.amoco.com (portal.trc.amoco.com) by netserv2 (4.1/SMI-4.0) id AA28798; Mon, 1 May 95 07:32:06 CDT Errors-To: x3j3-request@newton.ncsa.uiuc.edu Received: from newton.ncsa.uiuc.edu by portal.amoco.com with SMTP id AA04260 (InterLock SMTP Gateway 3.0 for ); Mon, 1 May 1995 07:31:24 -0500 Received: by newton.ncsa.uiuc.edu id AA05160 (5.65a/IDA-1.4.2 for jwagener@amoco.com); Mon, 1 May 95 07:04:06 -0500 Message-Id: <199505011126.AA23685@dkuug.dk> Date: 01 May 95 11:53:42 BST From: D Muxworthy Errors-To: x3j3-request@newton.ncsa.uiuc.edu X-Sequence: SC22WG5@dkuug.dk 799 Subject: (SC22WG5.799) WG5 Tokyo Resolutions To: sc22wg5@dkuug.dk X-Charset: ASCII X-Char-Esc: 29 ....................................................................... Item Subject: (SC22WG5.799) WG5 Tokyo Resolutions ISO/IEC JTC1/SC22/WG5 N1116 RESOLUTIONS OF THE WG5 MEETING ON 17 TO 21 APRIL 1995 IN TOKYO, JAPAN Resolutions T1 to T13 were passed by unanimous consent, T14 to T16 by unanimous acclaim. T1. Retiring Convenor of WG5 That WG5 expresses its utmost thanks for all the guidance and support its retiring convenor, Jeanne Martin, has given the Working Group over the past twelve years and for all the work she has done on behalf of Fortran and of standards more generally. T2. Convenor-elect of WG5 That WG5 welcomes the proposal of the British member body to assume the secretariat of WG5 and the nomination of Miles Ellis as convenor and urges all member bodies to endorse this nomination in the SC22 ballot. T3. Appreciation of X3J3 That WG5 expresses its most sincere appreciation to X3J3 for progressing development of the draft Fortran 95 document in accordance with the schedule in the Fortran strategic plan. T4. Content of Fortran 95 That WG5 intends to submit a draft revised standard for Fortran for CD ballot during the summer of 1995, and directs the editor to prepare a document (X3J3/95-007r1) by May 31, 1995 for this purpose. The content of this document will be WG5-N1094 (also known as X3J3/95-007) modified, within this time frame, as follows: items 1.1 to 1.10 of WG5-N1112, inclusive item 5 of WG5-N1112 together with any other technical corrections which may be identified during processing of the draft. The document for CD ballot should not contain further rationale sections (v. item 3.1 of WG5-N1112). If any portion of items 1.4 and 5 are not completed, the CD document will be as in WG5-N1094 in these respects. T5. Technical Corrigendum 3 That WG5 records its intent to produce a third, final, Technical Corrigendum for the current Fortran standard at the same time as the registration of the DIS for the revised standard. All corrections in this Technical Corrigendum will be incorporated in the DIS before submission to SC22. Publication of resolved defects is necessary since the Fortran 90 standard may be the basis of legal or other contractual requirements. T6. Electronic Distribution of Documents That WG5 endorses the principles for electronic distribution of WG5 documents outlined in WG5-N1077 and requests its acting convenor to determine the preferences of all its members. Further WG5 requests its acting convenor and Jamie Shiers to establish at CERN a WG5 ftp archive and a WG5 WWW home page and to arrange for copies to be held at subsidiary sites as may be required. T7. Development of Fortran beyond Fortran 95 That WG5 will respond more quickly to the needs of the Fortran community by aggressively pursuing Technical Reports of Type 2 between versions of the Fortran standard, with the intent that the material of such technical reports be integrated into the following revision of the Fortran standard. Document WG5-N1111 describes in detail the objectives and nature of these technical reports. Accordingly, WG5 directs its acting convenor to submit proposals to the SC22 secretariat for new work items for the production of these technical reports in time for a decision to be made at the SC22 plenary meeting, to be held in Annapolis in September 1995. T8. Handling Floating Point Exceptions That WG5 intends to produce a Technical Report in 1996 on handling floating point exceptions in Fortran; Wolfgang Walter is appointed interim Project Editor and is charged to assemble a development body and to identify a Project Editor. The target schedule and initial content of this technical report are described in document WG5-N1117. T9. Interoperability with C That WG5 intends to produce a Technical Report in 1996 on interoperability with C; Jamie Shiers is appointed interim Project Editor and is charged to assemble a development body and to identify a Project Editor. The target schedule and outline content of this technical report are described in document WG5-N1114. T10. Data Type Enhancements That WG5 intends to produce a Technical Report on handling data type enhancements that include allocatable components and parameterized derived types; Lawrie Schonfelder is appointed interim Project Editor and is charged to assemble a development body and to identify a Project Editor. The target schedule and outline content of this technical report are described in document WG5-N1115. T11. Standard Preprocessor for Fortran That WG5 recognizes that preprocessing facilities are an important consideration for many members of the Fortran community. However WG5 does not believe that such facilities should be incorporated into the Fortran Standard (ISO/IEC IS 1539-1). WG5 therefore invites members and member bodies to make proposals for further action, including specification of requirements and nominations for project editor. T12. Varying Length Character Strings in Fortran - development of IS 1539-2 That WG5 will revise ISO/IEC IS 1539-2:1994 in line with the revision of ISO/IEC IS 1539:1991 and directs its acting convenor to make the necessary arrangements with the SC22 secretariat. T13. Fortran 2000 Revision That WG5 intends to produce a first detailed specification of the content of the 2000/2001 revision of Fortran at its November 1995 meeting and therefore requests member bodies to submit requirements to the convenor no later than 15 September, 1995. Further, John Reid as editor of the WG5 Repository of Requirements (Standing Document 5), is directed to remind members of the conditions for, and the electronic format of the content of, submissions to the repository. T14. Vote of Thanks for Support for Meeting That WG5 thanks the Japanese member body (Information Processing Society of Japan/Information Technology Standards Commission of Japan), Fujitsu, Hitachi and NEC for generously supporting the meeting. T15. Vote of Thanks for Support for Mailing That WG5 thanks The Numerical Algorithms Group Ltd. for copying and distributing papers for WG5, including those for this meeting. T16. Vote of Thanks That WG5 wishes to express its appreciation to the acting convenor (Miles Ellis), the secretary (Malcolm Cohen), the drafting committee and the hosts (Hideo Wada, Masayuki Takata, Kazuo Nishimura, Minoru Tanaka, Yukimasa Yoshida and Ichiro Honma) for their contributions to the success of the meeting. Further that WG5 wishes especially to thank all the hosts for the exceptional kindness and hospitality shown to visitors throughout the meeting and for the arrangements made for the visit to Kamakura on the day preceding the meeting. ....................................................................... Item Subject: 95-005.RTF {\rtf1\ansi \deff4\deflang1033{\fonttbl{\f4\froman\fcharset0\fprq2 Times New Roman;}}{\colortbl;\red0\green0\blue0;\red0\green0\blue255;\red0\green255\blue255;\red0\green255\blue0;\red255\green0\blue255;\red255\green0\blue0; \red255\green255\blue0;\red255\green255\blue255;\red0\green0\blue128;\red0\green128\blue128;\red0\green128\blue0;\red128\green0\blue128;\red128\green0\blue0;\red128\green128\blue0;\red128\green128\blue128;\red192\green192\blue192;}{\stylesheet{\f4\fs20 \snext0 Normal;}{\*\cs10 \additive Default Paragraph Font;}}{\info{\author Authorized Gateway Customer}{\operator Cubicle B2}{\creatim\yr1995\mo4\dy24\hr14\min57}{\revtim\yr1995\mo4\dy27\hr15\min39}{\printim\yr1995\mo4\dy27\hr15\min39}{\version6} {\edmins20}{\nofpages0}{\nofwords0}{\nofchars0}{\vern49203}}\margt1008\margb720 \widowctrl\ftnbj\aenddoc\formshade \fet0\sectd \linex0\endnhere {\*\pnseclvl1\pnucrm\pnstart1\pnindent720\pnhang{\pntxta .}}{\*\pnseclvl2\pnucltr\pnstart1\pnindent720\pnhang {\pntxta .}}{\*\pnseclvl3\pndec\pnstart1\pnindent720\pnhang{\pntxta .}}{\*\pnseclvl4\pnlcltr\pnstart1\pnindent720\pnhang{\pntxta )}}{\*\pnseclvl5\pndec\pnstart1\pnindent720\pnhang{\pntxtb (}{\pntxta )}}{\*\pnseclvl6\pnlcltr\pnstart1\pnindent720\pnhang {\pntxtb (}{\pntxta )}}{\*\pnseclvl7\pnlcrm\pnstart1\pnindent720\pnhang{\pntxtb (}{\pntxta )}}{\*\pnseclvl8\pnlcltr\pnstart1\pnindent720\pnhang{\pntxtb (}{\pntxta )}}{\*\pnseclvl9\pnlcrm\pnstart1\pnindent720\pnhang{\pntxtb (}{\pntxta )}}\pard\plain \qr \f4\fs20 X3J3/95-005r1 \par \pard \qr Page 1 of 1 \par \pard \par \pard \qc {\b\fs28 X3J3 Responses to WG5 Tokyo Resolutions \par }\pard \par \pard T4. {\ul Content of Fortran 95} \par \pard \li360 X3J3 concurs with this resolution and will submit a document consistent with it soon after X3J3 meeting #133 (1995 April 24-28). \par \pard \par \pard T5. {\ul Technical Corrigendum 3 (TC3)} \par \pard \li360 X3J3 concurs with this resolution and will incorporate the edits associated with TC1, TC2, and TC3 into the Fortran 95 DIS. \par \pard \par \pard T6. {\ul Electronic Distribution of Documents} \par \pard \fi360 X3J3 supports this resolution. \par \pard \par \pard T7. {\ul Development of Fortran beyond Fortran 95} \par \pard \li360 X3J3 is apprehensive about the TR model being used to add functionality to the Fortran standard. Nevertheless, X3J3 will work with the development bodies to produce technically complete and accurate TRs. The process that X3J3 will use and the concerns raised by the TR process are detailed in X3J3/95-128r1. \par \pard \par \pard T8. {\ul Handling Floating Point Exceptions} \par \pard \li360 Subject to the general comments in the response to resolution T7, X3J3 concurs with the need for this functionality and agrees with the direction proposed by ISO/IEC JTC1/SC22/WG5 N1117. X3J3 appoints the following X3J3 members to the TR development body : \par \pard \par \pard T9. {\ul Interoperability with C} \par \pard \li360 Subject to the general comments in the response to resolution T7, X3J3 concurs with the need for this functionality. X3J3 recommen d that the development body concentrate on data interoperability and seriously consider the approach to interoperability expressed in ISO/IEC JTC1/SC22/WG5 N1096 and X3J3/95-114. X3J3 appoints the following X3J3 members to the TR development body: \par \pard \par \pard T10. {\ul Data Type Enhancements} \par \pard \li360 Subject to the general comments in the response to resolution T7, X3J3 concurs with the need for allocatable components. X3J3 does not believe that parameterized derived types meet the criteria set forth in ISO/IEC JTC1/SC22/WG5 N111 1. X3J3 strongly requests that WG5 remove parameterized derived types from this TR. X3J3 appoints the following X3J3 members to the TR development body: \par \pard \par \pard T11. {\ul Standard Preprocessor for Fortran} \par \pard \li360 X3J3 concurs with this resolution. \par \pard \par \pard T12. {\ul Varying Length Character Strings} ... \par \pard \li360 X3J3 concurs with this resolution but notes that a US suggested requirement for Fortran 2000 is an intrinsic varying length character string data type. \par \pard \par \pard T13. {\ul Fortran 2000 Revision} \par \pard \li360 X3J3 concurs with this resolution and intends to submit an updated and refined list of suggested Fortran 2000 requirements from the US. \par } ....................................................................... Item Subject: 95-128R1.RTF {\rtf1\ansi \deff4\deflang1033{\fonttbl{\f1\froman\fcharset2\fprq2 Symbol;}{\f4\froman\fcharset0\fprq2 Times New Roman;}}{\colortbl;\red0\green0\blue0;\red0\green0\blue255;\red0\green255\blue255;\red0\green255\blue0; \red255\green0\blue255;\red255\green0\blue0;\red255\green255\blue0;\red255\green255\blue255;\red0\green0\blue128;\red0\green128\blue128;\red0\green128\blue0;\red128\green0\blue128;\red128\green0\blue0;\red128\green128\blue0;\red128\green128\blue128; \red192\green192\blue192;}{\stylesheet{\widctlpar \f4\fs20 \snext0 Normal;}{\*\cs10 \additive Default Paragraph Font;}{\s15\widctlpar\tqc\tx4320\tqr\tx8640 \f4\fs20 \sbasedon0\snext15 header;}{\s16\widctlpar\tqc\tx4320\tqr\tx8640 \f4\fs20 \sbasedon0\snext16 footer;}{\*\cs17 \additive\sbasedon10 page number;}}{\info{\title To: X3J3 \'09\'09\'09\'09\'09\'09X3J3/95-}{\author SET Demo}{\operator SET Demo}{\creatim\yr1995\mo4\dy25\hr15\min22} {\revtim\yr1995\mo4\dy26\hr14\min41}{\version5}{\edmins141}{\nofpages0}{\nofwords0}{\nofchars0}{\vern49221}}\widowctrl\ftnbj\aenddoc\formshade \fet0\sectd \linex0\endnhere {\header \pard\plain \s15\widctlpar\tqc\tx4320\tqr\tx8640 \f4\fs20 {\field{\*\fldinst {\cs17 PAGE }}{\fldrslt {\cs17 2}}}{\cs17 \tab }{\cs17\b\fs28 X3J3/95-128r1} \par }{\*\pnseclvl1\pnucrm\pnstart1\pnindent720\pnhang{\pntxta .}}{\*\pnseclvl2\pnucltr\pnstart1\pnindent720\pnhang{\pntxta .}}{\*\pnseclvl3\pndec\pnstart1\pnindent720\pnhang{\pntxta .}}{\*\pnseclvl4\pnlcltr\pnstart1\pnindent720\pnhang{\pntxta )}}{\*\pnseclvl5 \pndec\pnstart1\pnindent720\pnhang{\pntxtb (}{\pntxta )}}{\*\pnseclvl6\pnlcltr\pnstart1\pnindent720\pnhang{\pntxtb (}{\pntxta )}}{\*\pnseclvl7\pnlcrm\pnstart1\pnindent720\pnhang{\pntxtb (}{\pntxta )}}{\*\pnseclvl8\pnlcltr\pnstart1\pnindent720\pnhang {\pntxtb (}{\pntxta )}}{\*\pnseclvl9\pnlcrm\pnstart1\pnindent720\pnhang{\pntxtb (}{\pntxta )}}\pard\plain \widctlpar \f4\fs20 To: X3J3 \tab \tab \tab \tab \tab \tab {\b\fs28 \par }From: /jor \par Subject:\tab X3J3 Response to Tokyo Resolution 7 \par \par X3J3 has reviewed the TR processing as proposed by WG5 and, although X3J3 has some concerns about the process and its effect on Fortran 2 000, X3J3 believes that establishing close liaison with the TR development bodies will produce both the best technical result for the TR and minimize future integration problems for Fortran 2000. \par \par To ameliorate some of these concerns, X3J3 proposes to collaborate with WG5\rquote s TR process as follows: \par \pard \widctlpar \par {\pntext\pard\plain\f1\fs20 \'b7\tab}\pard \fi-360\li360\widctlpar{\*\pn \pnlvlblt\ul\pnf1\pnstart1\pnindent360\pnhang{\pntxtb \'b7}} X3J3 will establish a subgroup for each TR. No more than three members of the X3J3 subgroup will be part of the TR development body. Any X3J3 member may participate in the electronic discussions of the TR development as she/he sees fit. \par \pard \widctlpar \par {\pntext\pard\plain\f1\fs20 \'b7\tab}\pard \fi-360\li360\widctlpar{\*\pn \pnlvlblt\ul\pnf1\pnstart1\pnindent360\pnhang{\pntxtb \'b7}} The X3J3 subgroup will be responsible for keeping X3J3 informed about the progress and content of the TR development and will communicate to the TR editor any editorial or integration concerns that X3J3 may raise. \par \pard \widctlpar \par {\pntext\pard\plain\f1\fs20 \'b7\tab}\pard \fi-360\li360\widctlpar{\*\pn \pnlvlblt\ul\pnf1\pnstart1\pnindent360\pnhang{\pntxtb \'b7}} The X3J3 subgroup will draw on any X3J3 expertise available to ensure the technical accuracy and completeness of the TR. \par \pard \widctlpar \par X3J3 is concerned with the manner in which WG5 decided to use the Type 2 Technical Reports as a mechanism to develop Fortran 2000. In particular , there was no open discussion within the WG5 membership prior to making this important decision -- indeed, most of the membership was not aware of this proposal before the proposal was presented and adopted at a sparsely-attended WG5 meeting. Thus, the re was limited consideration of the procedures to develop TRs, the interaction among the TRs, the proliferation of the TRs, and the interaction of the TRs with the Primary Development Body\rquote s work on the next revision of the standard. X3J3\rquote s concerns are as follows: \par \pard \widctlpar \par {\pntext\pard\plain\f1\fs20 \'b7\tab}\pard \fi-360\li360\widctlpar{\*\pn \pnlvlblt\ul\pnf1\pnstart1\pnindent360\pnhang{\pntxtb \'b7}} WG5 indicates that the TRs are considered as beta tests for language features and implementations, and yet requires the incorporation of the feature into Fortran 2000 without change, except for errors detected. These two concepts are not compatible beca use the purpose of a beta test is to find errors, better ways to define a feature, or features that are unused or unnecessary. These latter defects may not be corrected with the current procedures. Indeed, there is no possibility of rejecting the TR in Fortran 2000, even in the case that no implementations occur or it is generally agreed that the TR feature is not useful. \par \pard \widctlpar \par {\pntext\pard\plain\f1\fs20 \'b7\tab}\pard \fi-360\li360\widctlpar{\*\pn \pnlvlblt\ul\pnf1\pnstart1\pnindent360\pnhang{\pntxtb \'b7}} WG5 has established three TRs at the Tokyo meeting. The TR model for language development is that each TR is added to Fortran 95, one at a time. X3J3 is assuming that as a TR is created, the TR is required to specify its interaction with existing TRs a s well as Fortran 95. After the TRs are defined, X3J3 assumes that the respective development bodies are responsible for ma intaining the TRs, including responding to defect reports, particularly as more TRs are added and inconsistencies amongst them are discovered. \par \pard \widctlpar \par {\pntext\pard\plain\f1\fs20 \'b7\tab}\pard \fi-360\li360\widctlpar{\*\pn \pnlvlblt\ul\pnf1\pnstart1\pnindent360\pnhang{\pntxtb \'b7}} WG5 document N1111 suggests a small number of new features will be processed as TRs. In this context, particularly because of the interaction with the three major features required by WG5, three is already considered by many to be too large a number. We strongly recommend that any new proposal for a TR be allowed to gather consensus within the Fortran community. \par \pard \widctlpar \par In essence, FORTRAN 77, Fortran 90, and Fortran 95 were created in this incremental manner with documents describing the functionality, syntax, and semantics of a particular collection of features. It turned out in all three cases that the integration of the features was the most time-consuming and difficult aspect of the process, even when the syntax and semantics were permitted to change to allow the features to co-exist seamlessly. The TR process is highly constrained during the process of integratio n into \par \pard \widctlpar Fortran 2000, and therefore will not lead to seamless integration of features in Fortran 2000, particularly if there are a large number of TRs. X3J3 assumes that highly desirable extensions to a TR discovered during integration may be included in Fortra n 2000. \par }