From owner-sc22wg5+sc22wg5-dom8=www.open-std.org@open-std.org Wed Oct 25 22:21:38 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 39984358A30; Wed, 25 Oct 2017 22:21:38 +0200 (CEST) Delivered-To: sc22wg5@open-std.org X-Greylist: delayed 490 seconds by postgrey-1.34 at www5.open-std.org; Wed, 25 Oct 2017 22:21:37 CEST Received: from smtp-out-6.tiscali.co.uk (smtp-out-6.tiscali.co.uk [62.24.135.134]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by www.open-std.org (Postfix) with ESMTP id 2E699357125 for ; Wed, 25 Oct 2017 22:21:37 +0200 (CEST) Received: from [192.168.1.10] ([212.139.82.74]) by smtp.talktalk.net with SMTP id 7S3JevM4h0NSR7S3Je46JC; Wed, 25 Oct 2017 21:13:25 +0100 X-Originating-IP: [212.139.82.74] Subject: Straw ballot To: Steve Lionel , WG5 References: <20171024173005.992B3356DB8@www.open-std.org> From: John Reid Message-ID: <9d2b2f4c-3461-b2c2-62ad-32645173528d@stfc.ac.uk> Date: Wed, 25 Oct 2017 21:13:20 +0100 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:49.0) Gecko/20100101 Firefox/49.0 SeaMonkey/2.46 MIME-Version: 1.0 In-Reply-To: <20171024173005.992B3356DB8@www.open-std.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-CMAE-Envelope: MS4wfErYsPrd1LezJZTwkCrp5NYTYLzgqn9cCZhdGuIkkDRSndVah2PQIRwwA3kEVi2R9aoOO92+DnUAgUkYzaPNkNoGljjv+l+EVkvgpYpFhcT8jneTW58X yD6sCOfcy6dHQleIj1e7nqa1VAnDQGXStuNsFNdZFG4emCJcc4j03oQNPRdDv4brP15QECs8nVu8Zwn3MKDFMiYcoXFT7Uay5/uKMRFYi+96M2JPbowxx1BH tux4Uv4LtucMMZH1VlxggA== 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= 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. No Comment: We chose the name in 2015, see N2073, and have been using it ever since. We were well aware of the 3-year gap before publication, see N2070.