From owner-sc22wg5+sc22wg5-dom8=www.open-std.org@open-std.org Thu Oct 26 23:28:21 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 1A88C3587E3; Thu, 26 Oct 2017 23:28:21 +0200 (CEST) Delivered-To: sc22wg5@open-std.org X-Greylist: delayed 3604 seconds by postgrey-1.34 at www5.open-std.org; Thu, 26 Oct 2017 23:28:19 CEST Received: from mr91p64im-zteg11053801.me.com (mr91p64im-zteg11053801.me.com [17.120.88.12]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by www.open-std.org (Postfix) with ESMTP id CE83B356D02 for ; Thu, 26 Oct 2017 23:28:16 +0200 (CEST) Received: from process-dkim-sign-daemon.mr91p64im-zteg11053801.me.com by mr91p64im-zteg11053801.me.com (Oracle Communications Messaging Server 8.0.1.2.20170607 64bit (built Jun 7 2017)) id <0OYG00O0066ZL400@mr91p64im-zteg11053801.me.com> for sc22wg5@open-std.org; Thu, 26 Oct 2017 20:28:12 +0000 (GMT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=me.com; s=04042017; t=1509049692; bh=RnH8vdXS15HJp6ihpHel/AQRAS5AHqYFjpjyFycT2X8=; h=From:Content-type:MIME-version:Subject:Message-id:Date:To; b=f/Hg4vxfsX9mmZMHm/e54HGsvFotBLE1RyzWMwjwb12antdDDALdRBvGV0oTRi0DO 1UPbk8f/czxZZkhExuH9TMNNa3KOn1MDDc6Mp8Lx60ygw+PXK1Cv9LqllogDiC3ZY0 wQyt6vRq9bajr8LC13i35N3DWWk0+pfHfSWgIHIU1cpuXx33rhW1AShYjiR/oxiyak YbStbv933A2MVQpqDuUe56oWB4k+8bUwG8TvNbHf8rB0BDpA9tAYWN5iSzOFVLLadh Cg32SnITMiW6yTf3lo2EtlB/SU7Wjfgvmgc2GYmc7nIAOvrSjnXPkG8ANxiv9GA93J y5PbRm+ogObcw== Received: from icloud.com ([127.0.0.1]) by mr91p64im-zteg11053801.me.com (Oracle Communications Messaging Server 8.0.1.2.20170607 64bit (built Jun 7 2017)) with ESMTPSA id <0OYG00GY066Y0100@mr91p64im-zteg11053801.me.com> for sc22wg5@open-std.org; Thu, 26 Oct 2017 20:28:11 +0000 (GMT) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:,, definitions=2017-10-26_09:,, signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 clxscore=1011 suspectscore=0 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1707230000 definitions=main-1710260257 From: Dan Nagle Content-type: text/plain; charset=us-ascii Content-transfer-encoding: quoted-printable MIME-version: 1.0 (Mac OS X Mail 11.0 \(3445.1.7\)) Subject: straw ballot Message-id: <55649F1B-6DA8-45A1-B901-B7D912E6B9FD@me.com> Date: Thu, 26 Oct 2017 14:28:10 -0600 To: WG5 List X-Mailer: Apple Mail (2.3445.1.7) Sender: owner-sc22wg5@open-std.org Precedence: bulk Hi, YES 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. NO 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. Comment Fortran 2015 is today well known around the world to mean the next = standard, so a name change now creates a needless potential for confusion, and might be taken as = signaling difficulties. I endorse the comments of Reinhold Bader and John Reid on this question. -- Cheers! Dan Nagle