From jwagener@amoco.com Wed Feb 1 04:15:19 1995 Received: from interlock.amoco.com by dkuug.dk with SMTP id AA26290 (5.65c8/IDA-1.4.4j for ); Wed, 1 Feb 1995 17:15:59 +0100 Received: by interlock.amoco.com id AA02948 (InterLock SMTP Gateway 3.0 for sc22wg5@dkuug.dk); Wed, 1 Feb 1995 10:15:51 -0600 Message-Id: <199502011615.AA02948@interlock.amoco.com> Received: by interlock.amoco.com (Protected-side Proxy Mail Agent-3); Wed, 1 Feb 1995 10:15:51 -0600 Received: by interlock.amoco.com (Protected-side Proxy Mail Agent-2); Wed, 1 Feb 1995 10:15:51 -0600 Received: by interlock.amoco.com (Protected-side Proxy Mail Agent-1); Wed, 1 Feb 1995 10:15:51 -0600 From: jwagener@amoco.com X-Openmail-Hops: 1 Date: Wed, 1 Feb 95 10:15:19 -0600 Subject: informal JLW report on X3J3 meeting 132, 95 Jan 23-27, Houston To: sc22wg5@dkuug.dk X-Charset: ASCII X-Char-Esc: 29 Item Subject: Message text informal JLW report on X3J3 meeting 132, 95 Jan 23-27, Houston -------------------------------------------------------------- The goal of this meeting was to complete the 007 document integration work, with the objective of preparing a 95-007 document suitable for submission as a CD. Secondary objectives were to continue the Fortran 90 maintenance work and, time permitting, address other items in the premeeting distribution. A total of 35 papers were approved dealing with various aspects of document integration, 21 of them on Friday. Though by the end of Friday there was not a backlog of items ready for action, Friday was a very busy day with some papers appearing as late as that morning. There was no time for the subgroups to give their usual status summary, and one would have to conclude that the integration work was not completed. A deadline of March 3 was established for making 95-007 available on the X3J3 server; this document will be included in the WG5 premeeting distribution of March 6. Should the edits not be completed by that time, a list of remaining edits will also be available. During the month of March X3J3 will ballot this document in order to determine the US position at Tokyo; the ballot comments will be submitted as-is at the Tokyo meeting. A total of 11 interpretation items were addressed/passed, 9 of which will be on the post-meeting ballot (two made corrections to earlier interpretation actions). As a rough approximation, that leaves about 20 interpretation items still at the X3J3 consideration stage. During opening business on Monday the committee approved, by about a 2-1 margin, including an annex on rationale in Fortran 95. Discussion on the ensuing paper (95-052) on Thursday demonstrated considerable work to whip such an annex into shape and the committee consequently reversed its Monday action. Paper 95-052r1, which proposes a new feature rationale section in annex B, will be sent to the WG5 premeeting distribution. The crunch of integration items had not hit by Tuesday morning, so time permitted consideration of the subset ENABLE paper (95-026r1). After discussion a motion to accept this proposal for Fortran 95 failed by about a 2-1 margin. Finally, responses to the comments on the public review of withdrawing the Fortran 77 ANSI standard were discussed (95-056) and a subsequent motion failed to get the required 2/3 majority. It was decided to delay action on this issue pending clarification from NIST regarding NIST's plans for continued validation of Fortran (77 and 90) implementations against the current NIST validation suite. The next X3J3 meeting will be in Maui, Hawaii, the week following the Tokyo WG5 meeting in April. The main objective of that X3J3 meeting is expected to be to complete the CD document in accordance with the decisions made by WG5 in Tokyo. Jerry