From owner-sc22wg5+sc22wg5-dom8=www.open-std.org@open-std.org Mon Oct 30 19:05:39 2017 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 142613589A0; Mon, 30 Oct 2017 19:05:39 +0100 (CET) Delivered-To: sc22wg5@open-std.org X-Greylist: delayed 3602 seconds by postgrey-1.34 at www5.open-std.org; Mon, 30 Oct 2017 19:05:38 CET Received: from st13p21im-asmtp003.me.com (st13p21im-asmtp003.me.com [17.164.152.25]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by www.open-std.org (Postfix) with ESMTP id 8342B356D2C for ; Mon, 30 Oct 2017 19:05:36 +0100 (CET) Received: from process-dkim-sign-daemon.st13p21im-asmtp003.me.com by st13p21im-asmtp003.me.com (Oracle Communications Messaging Server 8.0.1.2.20170607 64bit (built Jun 7 2017)) id <0OYN00900B5LLS00@st13p21im-asmtp003.me.com> for sc22wg5@open-std.org; Mon, 30 Oct 2017 17:05:32 +0000 (GMT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=icloud.com; s=04042017; t=1509383132; bh=dQ2sFpdBYqM8GxG+QLGab5z7qBTtdmXd7eMuRyl4eL4=; h=Content-type:MIME-version:Subject:From:Date:Message-id:To; b=rp0oofA+vsDEm+k0qscQX/VnFs8gk8qYBk/TmXrJuLlMdQxfqNGtomzSf3fGFKL8z /2CXApND1+v5m/6/d6fANsGHcqoYfx3Nt8c1I76nbXERDKVQyP6JcK0QORBdH5CV0E fTWb0LtH4ry8uNp//0IbjLSznRaBrE+FQIdgrja3RN+GXnioi3ANzUkf9/8elIXbVi c1QeusMUIuJRsUKhtDu4H54MMYgCKrH93u2/3WJnzQgRB1KBNRK3VE/ypd4yr8DiWX iUNZmh5pvosbCzLsVGKiGrwemt8jMO4eFHBBOvPwyb6zjnWlaF0jJMjYnLzoUGQnaN cX2/BhlJTYMpA== Received: from icloud.com ([127.0.0.1]) by st13p21im-asmtp003.me.com (Oracle Communications Messaging Server 8.0.1.2.20170607 64bit (built Jun 7 2017)) with ESMTPSA id <0OYN00J5VBH67Q60@st13p21im-asmtp003.me.com> for sc22wg5@open-std.org; Mon, 30 Oct 2017 17:05:32 +0000 (GMT) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:,, definitions=2017-10-30_06:,, signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 clxscore=1015 suspectscore=4 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1707230000 definitions=main-1710300228 Content-type: text/plain; charset=us-ascii MIME-version: 1.0 (Mac OS X Mail 9.3 \(3124\)) Subject: Re: (SC22WG5.5988) Let's start over on the straw ballot From: David Muxworthy In-reply-to: <20171024173005.992B3356DB8@www.open-std.org> Date: Mon, 30 Oct 2017 17:05:29 +0000 Reply-to: David Muxworthy Content-transfer-encoding: quoted-printable Message-id: <231B9BB6-EEC1-4893-A2A6-DD11EDBBB17C@icloud.com> References: <20171024173005.992B3356DB8@www.open-std.org> To: sc22wg5@open-std.org X-Mailer: Apple Mail (2.3124) Sender: owner-sc22wg5@open-std.org Precedence: bulk Do you approve making the technical change to add a requirement that the = variable specified for STAT=3D in MOVE_ALLOC and the ATOMIC_xxx = intrinsics have a minimum decimal range of 4? See J3 paper 17-219 for = details. YES Do you approve disallowing a coarray or coindexed variable on the left = side of an intrinsic assignment statement if it is an unallocated = allocatable variable? This is an incompatibility with Fortran 2008 which = did not disallow this. See J3 paper 17-228 for details. YES Do you approve making the technical change to disallow coarrays of = TEAM_TYPE? See J3 papers 17-202r1 and 17-250r2 for details. YES Do you approve, after making changes passed at J3 meeting 214, creating = a Draft International Standard (DIS) and sending it for ballot? This = would meet the current development schedule. YES Do you approve changing the informal name of the in-development Fortran = standard from "Fortran 2015" to "Fortran 2018"? See J3 paper 17-193r1 = for details. YES (with comment) The content of the language revision was specified in broad terms in 2015 but detailed development has continued and even now is not finalized. Hence 2017 or 2018 would be a more appropriate name. What finally became Fortran 90 had three previous names (82, 8X, 88). The committee felt able to change the name to match reality. Outside its immediate community Fortran is widely seen as a legacy language, somewhat on a par with COBOL. For example in classifying its specialist groups the British Computer Society recently allocated Fortran to 'History of computing' rather than to 'Software development'. I am repeatedly asked such things as 'Is Fortran still going?' and 'Why are you wasting your time on such an old language?'. Hence to publish Fortran 2015 in 2018 (a three-year backward gap being longer than for any previous revision) would, in the wider world, only tend to reinforce the perception of Fortran as being behind the times.