From owner-sc22wg5+sc22wg5-dom8=www.open-std.org@open-std.org Thu Jan 28 20:57:36 2016 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 207F03572EC; Thu, 28 Jan 2016 20:57:35 +0100 (CET) Delivered-To: sc22wg5@open-std.org X-Greylist: delayed 653 seconds by postgrey-1.34 at www5.open-std.org; Thu, 28 Jan 2016 20:57:34 CET Received: from esa2.cray.iphmx.com (esa2.cray.iphmx.com [68.232.143.164]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by www.open-std.org (Postfix) with ESMTP id E3E65356F47 for ; Thu, 28 Jan 2016 20:57:32 +0100 (CET) DomainKey-Signature: s=cray1024; d=cray.com; c=nofws; q=dns; h=X-IronPort-AV:X-Cray-OBMMKR:Received:Received:Received: From:To:CC:Subject:Thread-Topic:Thread-Index:Date: Message-ID:References:In-Reply-To:Accept-Language: Content-Language:X-MS-Has-Attach:X-MS-TNEF-Correlator: x-originating-ip:Content-Type:Content-ID: Content-Transfer-Encoding:MIME-Version:Return-Path; b=ZhltjmO6dq8Ce2g7J0YUnvLzzfIkNHBs4fvzYQ1hKGXirDp6a5DxuKMd 85CTcqVzZ67flk/SGbaELknAPt+onG9achXRXcURXcv5mkQPOn8/AZ3Mu 0VOR4EF8kvlSiLofAUpfSlZhjgBB1KLsg7qhuIaXcAJrx18SlTdj0yXTX Y=; DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=cray.com; i=@cray.com; q=dns/txt; s=cray1024; t=1454011055; x=1485547055; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=t8YiQzbwo3km0PlZbAsmyNADbGhK3fjqBpXbhFaJ5FY=; b=zWz1MDCaJu85Y9Hr4t4+vcFHvhDKZhYKoyDHXf+pDuF8vPD/yBYiAf2d SWK1pk8cFKGRqWgSsIQIjLxDwowVYR0rpVRqmgyyHNk/gejUpiDK3mLW7 oX05obJvZpTA2ADhtEsuA+xmkhwvQtfzd4vH0XAGz+5XpAoOxXQ8Ha8Z2 4=; X-IronPort-AV: E=Sophos;i="5.22,360,1449532800"; d="scan'208";a="6238649" X-Cray-OBMMKR: 1433258124 6238649 Received: from cray-smtp-2.cray.com (HELO CFWEX01.americas.cray.com) ([136.162.34.11]) by esa2.cray.iphmx.com with ESMTP/TLS/AES256-SHA; 28 Jan 2016 19:46:35 +0000 Received: from CFWEXHYBRID.americas.cray.com (172.30.88.178) by CFWEX01.americas.cray.com (172.30.88.25) with Microsoft SMTP Server (TLS) id 14.3.224.2; Thu, 28 Jan 2016 13:46:34 -0600 Received: from CFWEX01.americas.cray.com ([169.254.1.240]) by cfwexhybrid.americas.cray.com ([::1]) with mapi id 14.03.0224.002; Thu, 28 Jan 2016 13:46:33 -0600 From: Bill Long To: Van Snyder , fortran standards email list for J3 CC: WG5 Subject: Re: (j3.2006) (SC22WG5.5656) [ukfortran] Straw ballot on second draft corrigendum4 Thread-Topic: (j3.2006) (SC22WG5.5656) [ukfortran] Straw ballot on second draft corrigendum4 Thread-Index: AQHRWgOTDgoIN80goEmvmXH50BEKMp8RuboA Date: Thu, 28 Jan 2016 19:46:33 +0000 Message-ID: <7155D63A-8965-4BAC-B757-7B6E46D9811C@cray.com> References: <20160121143417.3C8EF358651@www.open-std.org> <20160128084819.5A04435852E@www.open-std.org> <1454009948.6222.124.camel@math.jpl.nasa.gov> In-Reply-To: <1454009948.6222.124.camel@math.jpl.nasa.gov> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [172.31.22.59] Content-Type: text/plain; charset="Windows-1252" Content-ID: <456E426955ABE24AAA88D496AAD7AAF4@cray.com> Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Sender: owner-sc22wg5@open-std.org Precedence: bulk The =93active image=94 term is new in the TS/Fortran 2015. For edits to Fo= rtran 2008, it would not be appropriate. I assume Malcolm will make amy ne= eded adjustments when incorporating text into the Fortran 2015 draft.=20 Cheers, Bill On Jan 28, 2016, at 1:39 PM, Van Snyder wrote: > We're now using (or going to use) the term "active image" instead of > "non-stopped image". Should the two occurrences (6.7.1.2 and 6.7.3.2) > of "non-stopped image" be "active image"? >=20 > On Thu, 2016-01-28 at 17:49 +0900, Cohen Malcolm wrote: >> This is an interim vote. I might have other changes to suggest later (I= am=20 >> only 1/4 of the way through...). >>=20 >>> Please answer the following question "Is N2095, with the references and >>> notes removed, acceptable for submission to SC22 for publication as >>> Corrigendum 4 for Fortran 2008?" in one of these ways. >>>=20 >>> 1) Yes. >>> 2) Yes, but I recommend the following changes. >>=20 >> Yes, but I recommend the following changes. >>=20 >>> 3) No, for the following reasons. >>> 4) Abstain. >>=20 >> CHANGES: >> (1) In the edit for F08/0131 (page xvi), after "A contiguous array" inse= rt=20 >> the word "variable". This is because the sentence later says "provided = the=20 >> variable ..." and this is meant to apply both to the contiguous array or= the=20 >> scalar character variable. >> (2) Same edit, slightly later in the sentence, change "kind and kind typ= e=20 >> parameter" to "type and kind type parameter (if any)". This is obviousl= y=20 >> what the interp was talking about - the edit should not be insisting tha= t=20 >> the kind be interoperable twice. The "(if any)" is because I think this= can=20 >> apply when the array is of a BIND(C) type, which has no type parameter. >> (3) In the edit for F08/0127, change "is permitted to" to "can", i.e. th= e=20 >> replacement text should read "A free form continuation line can begin wi= th=20 >> ...". Reason: the Introduction is non-normative so we are not allowed t= o=20 >> have requirements here. >> (4) In the edit for F08/0124, the location should be "Subclause 1.3", an= d=20 >> the instruction should be "After the definition of parent component=20 >> (1.3.33.2), insert a new term:", as although definitions use the same=20 >> numbering scheme as subclauses, they are not actually subclauses: see I= SO=20 >> directives part 2 which says >> "terms and definitions are a definitions list and not a series of=20 >> subclauses". >> (5) Subclause 4.3.1.3 >> Change "the derived-type-def of the specified derived type" to "i= ts=20 >> derived-type-def". >> Reason: immediately prior to this we've established that we are talking= =20 >> about "that derived type" (which is "the derived type [] specified in th= e=20 >> FUNCTION statement"); switching from "that derived type" to "the specifi= ed=20 >> derived type" implies there is some other specified derived type (which = is=20 >> not the case) as well as being unnecessarily long-winded platitudinous=20 >> ponderosity. "its" is more than adequate! >> (6) It does not really matter for a corrigendum, but the edit for 5.3.4= =20 >> inserts a disjunction into a paragraph that already has a conjunction,=20 >> without adding a comma for disambiguation. One can deduce the parse fro= m=20 >> the fact that it has bullet points, but it would be slightly nicer if th= ere=20 >> were also a comma before the "and" at the end of the first bullet point.= (I=20 >> will have to remember this when applying the changes to 007!) >>=20 >> Cheers, >=20 >=20 > _______________________________________________ > J3 mailing list > J3@mailman.j3-fortran.org > http://mailman.j3-fortran.org/mailman/listinfo/j3 Bill Long = longb@cray.com Fortran Technical Support & voice: 651-6= 05-9024 Bioinformatics Software Development fax: 651-605-9142 Cray Inc./ Cray Plaza, Suite 210/ 380 Jackson St./ St. Paul, MN 55101