From jwagener@trc.amoco.com Fri Nov 20 07:33:36 1992
Received: from noc.msc.edu by dkuug.dk with SMTP id AA10722
  (5.65c8/IDA-1.4.4j for <SC22WG5@dkuug.dk>); Fri, 20 Nov 1992 20:37:42 +0100
Received: from uc.msc.edu by noc.msc.edu (5.65/MSC/v3.0.1(920324))
	id AA29177; Fri, 20 Nov 92 13:37:50 -0600
Received: from [149.180.11.2] by uc.msc.edu (5.65/MSC/v3.0z(901212))
	id AA26684; Fri, 20 Nov 92 13:37:48 -0600
Received: from trc.amoco.com (apctrc.trc.amoco.com) by netserv2 (4.1/SMI-4.0)
	id AA08198; Fri, 20 Nov 92 13:33:55 CST
Received: from crmac1 by trc.amoco.com (4.1/SMI-4.1)
	id AA05680; Fri, 20 Nov 92 13:33:36 CST
Date: Fri, 20 Nov 92 13:33:36 CST
Message-Id: <9211201933.AA05680@trc.amoco.com>
From: Jerrold L. Wagener <jwagener@trc.amoco.com>
To: SC22WG5@dkuug.dk
Subject: informal JLW report on X3J3 meeting 123
X-Charset: ASCII
X-Char-Esc: 29

Having now returned from Supercomputing '92, here is my brief, informal,  
summary of the Nov 9-13, 1992, X3J3 meeting in New Haven.

informal JLW report of X3J3 meeting 123, 1992 Nov 9-13 (New Haven)
------------------------------------------------------------------

The principal objectives of this meeting were to (1) process as many of the 
interpretation issues as possible, (2) generate a preliminary review of HPF, 
and (3) refine the X3J3 reorganization plan.  Good progress was made on all 
three of these objectives.

At the start of the meeting there were approximately 95 outstanding issues.  
These included old unresolved issues and S20 items not yet at the balloting 
stage as well as new RFIs, but not the 58 items on the S20 ballot.  During 
the meeting all the "unresolved issues" were either resolved or recast into 
S20 items.  At the end of the meeting there were a total of 118 S20 items, of 
which
             33 are "X3J3 approved; ready for WG5"
             45 are "X3J3 draft response" and ready for X3J3 ballot
             40 are still at "X3J3 consideration in progress"

Those of the 45 that pass the X3J3 ballot (which will probably occur in 
December) will be added to the 33 ready for WG5.

A team of three people (Bierman, Himer, Phillimore) spent the week as an ad 
hoc SWAT team to review HPF/v04, primarily from a "how does it fit with 
Fortran 90" point of view rather than a technical functionality point of 
view.  Generally HPF gets high marks on this score, though several straw 
votes were taken on suggestions for specific recommendations.  It was agreed 
that the BHP team would prepare a letter to HPF consistent with this 
direction, have one final email review on the X3J3+WG5 network, then send it 
off to HPF in time for their December meeting.  The main two straw votes 
taken were (1) "directives vs syntax" (directives won, but the basic form of 
the directives should be consistent with the syntax approach) and (2) "an HPF 
module, or no, for packaging the HPF intrinsic functions" (an HPF module won, 
as the best way of managing the namespace, with the USE HPF statement treated 
as an appropriate directive for the HPF subset).

Two important agreements were reached relative to the X3J3 organization.  
First, an object-oriented subgroup (X3J3/OOF) was formed to explore this 
area.  Members of /OOF currently are Katz, Lahey, and J.Martin, with Lahey 
acting as interim subgroup head.  Katz will arrange for an OO tutorial for 
the next meeting.  Second, it was decided to try to schedule the next few 
X3J3 meetings so that /OOF, /parallel, and /posix subgroup meetings will not 
overlap with the interpretation work, giving members an opportunity to 
participate in both.  (/editorial and possibly /JOD, renamed to 
/requirements, will likely work fulltime on 1995 revision issues.)

Finally the US TAG session on Friday afternoon developed a recommended US 
position on the SC22 Varying String ballot (N1267) and decided to communicate 
with the X3 secretariat on the recently established IPF (International 
Participation Fee).  On the N1267 ballot, the recommendation is that the US 
vote NO, for one procedural and four technical reasons.  The thrust of the 
IPF letter is to communicate possible consequences of this fee and to suggest 
constructive alternatives.  The next TAG meeting was set, subject to 
reconsideration if unexpected responsibilities materialize, for May 1993.

Jerry Wagener


