From owner-sc22wg5 Sun Jul 21 16:52:44 2002 Received: from ztxmail04.ztx.compaq.com (ztxmail04.ztx.compaq.com [161.114.1.208]) by dkuug.dk (8.9.2/8.9.2) with ESMTP id QAA79122 for ; Sun, 21 Jul 2002 16:52:43 +0200 (CEST) (envelope-from whitlock@bugsy.zko.dec.com) Received: from mailrelay01.cce.cpqcorp.net (mailrelay01.cce.cpqcorp.net [16.47.68.171]) by ztxmail04.ztx.compaq.com (Postfix) with ESMTP id 99E2E195D for ; Sun, 21 Jul 2002 09:52:48 -0500 (CDT) Received: from bugsy (bugsy.zko.dec.com [16.31.64.14]) by mailrelay01.cce.cpqcorp.net (Postfix) with SMTP id 4D164D96 for ; Sun, 21 Jul 2002 09:52:48 -0500 (CDT) Date: Sun, 21 Jul 2002 10:51:47 -0400 Message-Id: <02072110514759@bugsy.zko.dec.com> From: whitlock@bugsy.zko.dec.com (Stan Whitlock Intel Corp. (603)886-7642) To: SC22WG5@dkuug.dk Subject: J3 paper for meeting #162 -F95 interpretation status for WG5 and J3 X-VMS-To: SC22WG5@DKUUG.DK,CC J3 and WG5: Here is the current status of F95 interps for our August-2002 meeting. Mallory: Please give this a paper number for meeting 162 and put it on the server. Thanks /Stan ********************************************************************** 02-sjw162-1 Date: 21-Jul-2002 To: WG5 and J3 From: Stan Whitlock for J3/interp Subj: Current status of F95 interpretation processing I have submitted the following papers for J3 meeting #162: 02-006A.txt currently open F95 interpretations to be processed 02-006C1.txt F95 interpretations in Corrigendum #1 02-006C2.txt F95 interpretations in Corrigendum #2 These will become the J3 standing documents 006A, 006C1, and 006C2: 006C1 is equivalent to WG5/N1421. See N1422 for the F95 interpretations that make up Corrigendum #1. 006C1 will not be modified further. 006C2 is the equivalent of WG5/N1472. See N1473 for F95 interpretations that make up Corrigendum #2. 006C2 will not be modified further. 006A is based on WG5/N1474, the F95 interpretations as of 27-Nov-2001 that still needed processing aftedr Corrigendum #2 was completed. 006A will evolve into 006Ar1, etc, as more F95 interpretations are processed. Here is the table of contents for 02-006A.txt with the interpretations contained in Corrigenda #1 and #2 removed so we can see what is left to be processed: Part 0: Summary Status of these Fortran 95 Interpretations ====================================================================== Status S: Defect Type T: P == J3 consideration in progress C == Clarification M Passed by J3 meeting E Erratum B Passed by J3 letter ballot I Interpretation W Passed by WG5 ballot C1 Included in corrigendum 1 (see N1422) C2 Included in corrigendum 2 (see N1473) X Excluded for the reasons given S T number title - - ------ ----- P I 000000e Rejected Minor edits and corrections P I 000004 Value returned by MAXVAL/MINVAL P I 000006 Character length specification of a function result P I 000008 Optional arguments to MAX/MIN X 000013 Format of zero in list-directed and namelist output {questions duplicated in 000067} X 000016 Completely removed - duplicate of 000071 P I 000017 Characteristics of an array function result P E 000023 Termination of the previous record by a WRITE statement P 000030 Ordering requirements on definition of specification functions P E 000031 Association of pointer function result with INTENT(OUT) dummy argument P E 000068 Asterisks as I/O units P 000074 TARGET dummy arguments and POINTER expressions P 000078 Resolving generic procedure references P I 000096 End-of-record and PAD P 000098 Are dummy functions returning assumed-length character legal? P 000099 STAT= variable requirements in ALLOCATE P 000100 TARGET attribute and structure components P I F90/000049 Characteristics of function results P E F90/000070 Characteristics specified by interface bodies P E F90/000096 Definition of "Declaration" P E F90/000140 TARGET attribute for a derived-type object with a pointer component P E F90/000145 Expressions in of a FUNCTION statement P E F90/000180 Unambiguous generic references P F90/000206 Collating sequence inconsistencies P E F90/000207 Integer bit-model inconsistency P F90/000208 nonadvancing output followed by list directed output P F90/000210 nonadvancing write followed by list directed write M E JP-17 Multiple occurrence of namelist group object in namelist group M E JP-24 The bnf term shared-term-do-construct X JP-39 Withdrawn by submitter Please note that a new category as been added: "X" means "Excluded for the reasons given". This applies to interpretations that will not be considered for further processing: X 000013 Format of zero in list-directed and namelist output {questions duplicated in 000067} X 000016 Completely removed - duplicate of 000071 X JP-39 Withdrawn by submitter There are several interpretations whose status is incorrect in 02-006A for meetint #162. The following were marked as "Passed J3 meeting" but later failed a J3 letter ballot. They should be marked in 02-006A as "J3 consideration in progress. That corrected status is reflected in this paper. P I 000006 Character length specification of a function result {01-380 m159 failed J3 LB} P E 000031 Association of pointer function result with INTENT(OUT) dummy argument {01-275 m158 failed J3 LB} P E 000068 Asterisks as I/O unit {01-380 m159 failed J3 LB} P E F90/000207 Integer bit-model inconsistency {01-380 m159 failed J3 LB} There are several interpretations that have been passed by a J3 meeting and are eligible for a J3 letter ballot. There will be such a letter ballot after meeting #162. M E JP-17 Multiple occurrence of namelist group object in namelist group {02-130 at m160} M E JP-24 The bnf term shared-term-do-construct {02-131r1 at m160} There are 3 new F95 interpretations since N1474: P 000098 Are dummy functions returning assumed-length character legal? {m160} P 000099 STAT= variable requirements in ALLOCATE {m162} P 000100 TARGET attribute and structure components {m162} So if you do the math, there are 24 P to be processed 2 M to be J3 letter ballotted 3 X excluded from futher processing 1 P 000000e -- 30 in the list