ISO/IEC JTC1/SC22/WG5 N1685 Japan National Activity Report at the WG5 London meeting in August 6-10, 2007 by TAKATA Masayuki IPSJ/ITSCJ/SC22/Fortran WG has 8 active members (5 from venders and 3 from universities), and monthly meets face to face for one hour, after the meetings for Japanese version of Fortran 2003, for which 2 more active members are also working. The translation work, started in April, 2005, is behind the schedule. We hope it will be published within this year. We discussed the following topics at our recent meetings: (1) Schedule of the current revision Japan supports the 2-year shift proposed in N1682, for the same reasons as the UK stated. (2) Contents of the current revision At least one member strongly disagrees with the inclusion of the co-array feature in the base language; he says SPMD model or distributed memory model itself is not necessarily promised to be major for ever, even after co-array survived among competing programming styles. Taking this into account as well as the UK concerns, the suggestion to make co-arrays a TR would be a good compromise. We had no time to discuss each of other features, but the overall feeling that the draft made too big change, at this early stage after F2003, was dominant. BITS would be the first thing to remove from the draft, in this sense. (3) Possibility of the Tokyo meeting in 2008 Such a meeting is available, and we are happy to host it. A possible plan is outlined below: - in November, at Kikai Shinko Kaikan, where we usually meet - two meeting rooms, with wireless access - text/PDF printing and photo copying services - suggested hotels list provided (or group booking?) - supplied refreshments: coffee/tea/juice, 2 times a day - a light dinner or banquet sponsored by ITSCJ - meeting rooms need to be reserved one year ahead, and before that, the outlined plan, including precise dates and expected attendance, has to be shown and agreed at a monthly board meeting (4) Questions raised from the translation of F2003 There were more than forty of them, and after discussion, the following items are still questionable for us. We believe most, if not all, of these should be treated as editorial requests for the current revision, and would like to put this list here to avoid unnecessary input as new Interpretation requests. The page/line numbers below are those of the current WD F2008. - At p.70, l.8, in R432: Change "BIND (C)" to "BIND ( C )". - At p.92, l.13, in R463: Change "ENUM, BIND(C)" to "ENUM , BIND ( C )". - At p.227, l.10, just before Note 9.12: Change "highest-numbered position" to "position just after the highest- numbered file storage unit", in the following context: For a formatted stream output statement, if no error condition occurred, the terminal point of the file is set to the highest- numbered position to which data was transferred by the statement. - At p.273, l.17, in 10.2.1: Change "repeat specifier" to "repeat specification". - At p.295, l.4, and p.299, l.21, in 10.10.4 and 10.11.3.6: Change "decimal edit mode is comma" to "decimal edit mode is COMMA". - At p.305, l.6, in 11.2.2: Change "USE statement" into plain font. It's already made bold (as an index item) in the previous paragraph. - From p.314, l.34 to p.315, l.2, in R1208: Change "(" to "( ", and ")" to " )", four times for each. - At p.455, l.36, in 14.7: Change "and IEEE_GET_ROUNDING_MODE" to "IEEE_GET_ROUNDING_MODE, and IEEE_GET_UNDERFLOW_MODE". - At p.455, l.37, in 14.7: Change "and IEEE_SET_ROUNDING_MODE" to "IEEE_SET_ROUNDING_MODE, and IEEE_SET_UNDERFLOW_MODE". - At p.458, l.8, and p.464, l.20, in 14.10.3 and 14.11.15: Change "IEEE REM function" to "IEEE rem function". Other IEEE functions like "copysign" are written in lowercase. - At p.482, l.3, in 15.2.3.3: Add commas to the both ends of the inserted clause "if it is a pointer". -At p.513, l.44, in 16.6.6 (15): Change "(16.5.2.4-16.5.2.5)" to "(16.5.2.4, 16.5.2.5)". -At p.514, l.2, in 16.6.6 (17): Change "WAIT operation" to "wait operation". -At p.558 l.18, in C.7.3: Change '''THIS STRING HAS QUOTES.''' to '"THIS STRING HAS QUOTES."' (In F95, this example was correctly written.) -At p.589, l.14, in C.12.3: Add a colon at the end of the line "C Struct Declaration".