From owner-sc22wg5+sc22wg5-dom8=www.open-std.org@open-std.org Fri Jun 15 09:24:11 2012 Return-Path: X-Original-To: sc22wg5-dom8 Delivered-To: sc22wg5-dom8@www.open-std.org Received: by www.open-std.org (Postfix, from userid 521) id EB8E13568F0; Fri, 15 Jun 2012 09:24:10 +0200 (CEST) Delivered-To: sc22wg5@open-std.org Received: from mga09.intel.com (mga09.intel.com [134.134.136.24]) by www.open-std.org (Postfix) with ESMTP id EE0A03567F7 for ; Fri, 15 Jun 2012 09:24:08 +0200 (CEST) Received: from orsmga002.jf.intel.com ([10.7.209.21]) by orsmga102.jf.intel.com with ESMTP; 15 Jun 2012 00:24:06 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="4.67,351,1309762800"; d="scan'208,217";a="157928704" Received: from orsmsx606.amr.corp.intel.com ([10.22.226.128]) by orsmga002.jf.intel.com with ESMTP; 15 Jun 2012 00:24:06 -0700 Received: from orsmsx104.amr.corp.intel.com (10.22.225.131) by orsmsx606.amr.corp.intel.com (10.22.226.128) with Microsoft SMTP Server (TLS) id 8.2.255.0; Fri, 15 Jun 2012 00:24:06 -0700 Received: from orsmsx103.amr.corp.intel.com ([169.254.2.73]) by ORSMSX104.amr.corp.intel.com ([169.254.3.217]) with mapi id 14.01.0355.002; Fri, 15 Jun 2012 00:24:06 -0700 From: "Whitlock, Stan" To: WG5 CC: "Whitlock, Stan" Subject: J3/12-147r1 Fortran interp letter ballot #25 - now due 22-Jun-2012 Thread-Topic: J3/12-147r1 Fortran interp letter ballot #25 - now due 22-Jun-2012 Thread-Index: Ac1Kx9G86PWqxBwpR4y839hQvsFs0A== Date: Fri, 15 Jun 2012 07:24:05 +0000 Message-ID: <4AA982B1265F43408480F737BE12F4D313B58F@ORSMSX103.amr.corp.intel.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.22.254.140] Content-Type: multipart/alternative; boundary="_000_4AA982B1265F43408480F737BE12F4D313B58FORSMSX103amrcorpi_" MIME-Version: 1.0 Sender: owner-sc22wg5@open-std.org Precedence: bulk --_000_4AA982B1265F43408480F737BE12F4D313B58FORSMSX103amrcorpi_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable 12-147r1 To: J3 Members From: Stan Whitlock Subject: J3 Fortran interp letter ballot #25 - now due 22-Jun-2012 Date: 2012 Jun 15 Because of the unavailability of the J3 web site during the original voting period, the new deadline for interp letter ballot #25 replies is 22-Jun-2012. Please vote. Enclosed in the next letter ballot on Fortran interpretations. The rules by which we operate say: o J3 votes on the answer at a J3 meeting; a simple majority vote marks the answer as "passed by J3 meeting". o Between J3 meetings the chair of /interp sends a J3 letter ballot to J3 to approve interp answers that have been "passed by J3 meeting". The letter ballot runs for 30 days. Not voting on three of four consecutive J3 letter ballots is grounds to terminate J3 membership. An interp answer passes by a 2/3rds vote; a no vote must be accompanied by an explanation of the changes necessary to change the member's vote to yes. J3/interp reserves the right to recall an interp answer for more study even if the answer passes. 43 Fortran interpretations are currently "Passed by J3 meeting" after J3 meeting #197. This is the letter ballot phase to go from "Passed by J3 meeting" to "Passed by J3 letter ballot". The following Fortran interpretations are being balloted: Yes No Number Title --- --- F03/0017 Dummy procedure pointers and PRESENT --- --- F03/0018 Multiple identical specific procedures in type-bound generic interfaces --- --- F03/0019 Multiple identical specific procedures in generic interface blocks --- --- F03/0021 What kind of token is a stop code? --- --- F03/0046 Unlimited polymorphic pointers in common blocks --- --- F03/0053 The BIND attribute for C_PTR and C_FUNPTR --- --- F03/0065 Relational equivalence --- --- F03/0084 IEEE_SET_ROUNDING_MODE in a subroutine --- --- F03/0096 Can a read statement change the unit value? --- --- F03/0103 Restrictions on dummy arguments not present for polymorphic type or parameterized derived type --- --- F03/0116 indistinguishable specifics for a generic interface with use association --- --- F03/0118 Are lower bounds of assumed-shape arrays assumed? --- --- F03/0120 When are parameterized sequence types the same type? --- --- F03/0121 Precise FP semantics of the REAL intrinsic --- --- F08/0004 Is TARGET argument of ASSOCIATED a pointer or nonpointer dummy? --- --- F08/0008 IEEE exceptions for intrinsic functions --- --- F08/0031 PURE INTENT(OUT) finalization --- --- F08/0032 PURE FUNCTION result finalization --- --- F08/0038 Are pointless restrictions on DIM arguments intended? --- --- F08/0040 MOVE_ALLOC for coarrays --- --- F08/0042 SOURCE=3D questions --- --- F08/0043 Executing a type-bound procedure on a coindexed object --- --- F08/0048 Sequence association for coarrays --- --- F08/0054 Requirements for needing an explicit interface --- --- F08/0055 G editing for reals --- --- F08/0056 Non-polymorphic ALLOCATE with polymorphic SOURCE=3D --- --- F08/0057 Interoperability with empty types --- --- F08/0058 ENTRY point RESULT variable --- --- F08/0059 Auto-targetting requirements --- --- F08/0060 Procedure pointer assignment with an EXTERNAL target --- --- F08/0061 Description of the CONTIGUOUS attribute misworded? --- --- F08/0062 Mixing default initialization with DATA initialization --- --- F08/0063 G editing to a narrow output field --- --- F08/0064 STATUS of GET_ENVIRONMENT_VARIABLE --- --- F08/0065 Should certain procedures in intrinsic modules be pure? --- --- F08/0066 Are certain expressions with pointer initialization constant? --- --- F08/0067 Passing arrays of extended type objects --- --- F08/0068 Pointer association and extended type arrays --- --- F08/0069 Which part of an effective argument becomes undefined? --- --- F08/0070 Finalization of INTENT(OUT) arguments --- --- F08/0071 Vector subscript target --- --- F08/0072 Final subroutines with corank --- --- F08/0073 Polymorphic auto-targetting The text of these interpretations is attached at the end of paper 12-147. Each interpretation starts with a row of "-"s. Please mark the above -Y- in the Yes column for "yes", -C- in the Yes column for "yes with comment", or -N- in the No column for a "no" answer {be sure to include your reasons with "no"} and send only the above text {not this entire mail message} with any comments to j3@j3-fortran.org by 11:59:59PM, PDT, Friday, 22-Jun-2012, in order to be counted. Thanks /Stan ---------------------------------------------------------------------- Please see paper 12-147 for the complete text of the interps being voted on. --_000_4AA982B1265F43408480F737BE12F4D313B58FORSMSX103amrcorpi_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

        &nbs= p;            &= nbsp;           &nbs= p;            &= nbsp;            12-= 147r1

 

To:        J3 Mem= bers

From:      Stan Whitlock

Subject:   J3 Fortran interp letter ballot= #25 - now due 22-Jun-2012

Date:      2012 Jun 15=

 

 

Because of the unavailability of the J3 web site dur= ing the original

voting period, the new deadline for interp letter ba= llot #25 replies

is 22-Jun-2012.  Please vote.

 

Enclosed in the next letter ballot on Fortran interp= retations.

 

The rules by which we operate say:

 

    o   J3 votes on the ans= wer at a J3 meeting; a simple majority

        vote mark= s the answer as "passed by J3 meeting".

 

    o   Between J3 meetings= the chair of /interp sends a J3 letter

        ballot to= J3 to approve interp answers that have been "passed

        by J3 mee= ting".  The letter ballot runs for 30 days.  Not<= /p>

        voting on= three of four consecutive J3 letter ballots is

        grounds t= o terminate J3 membership.  An interp answer passes

        by a 2/3r= ds vote;  a no vote must be accompanied by an

        explanati= on of the changes necessary to change the member's

        vote to y= es.

 

        J3/interp= reserves the right to recall an interp answer for

        more stud= y even if the answer passes.

 

43 Fortran interpretations are currently "Passe= d by J3 meeting" after

J3 meeting #197.  This is the letter ballot pha= se to go from "Passed

by J3 meeting" to "Passed by J3 letter bal= lot".

 

The following Fortran interpretations are being ball= oted:

 

Yes  No   Number   &nb= sp; Title

 

---  ---  F03/0017   Dummy proce= dure pointers and PRESENT

---  ---  F03/0018   Multiple id= entical specific procedures in

        &nbs= p;             = type-bound generic interfaces

---  ---  F03/0019   Multiple id= entical specific procedures in

        &nbs= p;             = generic interface blocks

---  ---  F03/0021   What kind o= f token is a stop code?

---  ---  F03/0046   Unlimited p= olymorphic pointers in

        &nbs= p;             = common blocks

---  ---  F03/0053   The BIND at= tribute for C_PTR and C_FUNPTR

---  ---  F03/0065   Relational = equivalence

---  ---  F03/0084   IEEE_SET_RO= UNDING_MODE in a subroutine

---  ---  F03/0096   Can a read = statement change the unit value?

---  ---  F03/0103   Restriction= s on dummy arguments not present for

        &nbs= p;             = polymorphic type or parameterized derived type

---  ---  F03/0116   indistingui= shable specifics for a generic

        &nbs= p;             = interface with use association

---  ---  F03/0118   Are lower b= ounds of assumed-shape arrays assumed?

---  ---  F03/0120   When are pa= rameterized sequence types the same

        &nbs= p;             = type?

---  ---  F03/0121   Precise FP = semantics of the REAL intrinsic

---  ---  F08/0004   Is TARGET a= rgument of ASSOCIATED a pointer or

        &nbs= p;             = nonpointer dummy?

---  ---  F08/0008   IEEE except= ions for intrinsic functions

---  ---  F08/0031   PURE INTENT= (OUT) finalization

---  ---  F08/0032   PURE FUNCTI= ON result finalization

---  ---  F08/0038   Are pointle= ss restrictions on DIM arguments

        &nbs= p;             = intended?

---  ---  F08/0040   MOVE_ALLOC = for coarrays

---  ---  F08/0042   SOURCE=3D q= uestions

---  ---  F08/0043   Executing a= type-bound procedure on a coindexed

        &nbs= p;             = object

---  ---  F08/0048   Sequence as= sociation for coarrays

---  ---  F08/0054   Requirement= s for needing an explicit interface

---  ---  F08/0055   G editing f= or reals

---  ---  F08/0056   Non-polymor= phic ALLOCATE with polymorphic SOURCE=3D

---  ---  F08/0057   Interoperab= ility with empty types

---  ---  F08/0058   ENTRY point= RESULT variable

---  ---  F08/0059   Auto-target= ting requirements

---  ---  F08/0060   Procedure p= ointer assignment with an EXTERNAL target

---  ---  F08/0061   Description= of the CONTIGUOUS attribute misworded?

---  ---  F08/0062   Mixing defa= ult initialization with DATA

        &nbs= p;             = initialization

---  ---  F08/0063   G editing t= o a narrow output field

---  ---  F08/0064   STATUS of G= ET_ENVIRONMENT_VARIABLE

---  ---  F08/0065   Should cert= ain procedures in intrinsic modules be

        &nbs= p;             = pure?

---  ---  F08/0066   Are certain= expressions with pointer initialization

        &nbs= p;             = constant?

---  ---  F08/0067   Passing arr= ays of extended type objects

---  ---  F08/0068   Pointer ass= ociation and extended type arrays

---  ---  F08/0069   Which part = of an effective argument becomes

        &nbs= p;             = undefined?

---  ---  F08/0070   Finalizatio= n of INTENT(OUT) arguments

---  ---  F08/0071   Vector subs= cript target

---  ---  F08/0072   Final subro= utines with corank

---  ---  F08/0073   Polymorphic= auto-targetting

 

The text of these interpretations is attached at the= end of paper

12-147.  Each interpretation starts with a row = of "-"s.

 

Please mark the above -Y- in the Yes column for &quo= t;yes", -C- in the Yes

column for "yes with comment", or -N- in t= he No column for a "no"

answer {be sure to include your reasons with "n= o"} and send only the

above text {not this entire mail message} with any c= omments to

 

        j3@j3-for= tran.org

 

by 11:59:59PM, PDT, Friday, 22-Jun-2012, in order to= be counted.

 

 

Thanks       &nbs= p;            &= nbsp;    /Stan

 

----------------------------------------------------= ------------------

 

Please see paper 12-147 for the complete text of the= interps being

voted on.

 

 

 

--_000_4AA982B1265F43408480F737BE12F4D313B58FORSMSX103amrcorpi_--