From owner-sc22wg5+sc22wg5-dom8=www.open-std.org@open-std.org Mon Oct 9 20:51:41 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 4314F35899D; Mon, 9 Oct 2017 20:51:41 +0200 (CEST) Delivered-To: sc22wg5@open-std.org Received: from mail.jpl.nasa.gov (smtp.jpl.nasa.gov [128.149.139.109]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by www.open-std.org (Postfix) with ESMTP id 80667356834 for ; Mon, 9 Oct 2017 20:51:37 +0200 (CEST) Received: from [137.79.7.57] (math.jpl.nasa.gov [137.79.7.57]) by smtp.jpl.nasa.gov (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.1) with ESMTP id v99IpXqi002228 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128 bits) verified NO) for ; Mon, 9 Oct 2017 11:51:35 -0700 Subject: [Fwd: ISO/IEC JTC 1/SC 22/WG 5 New documents available on ISOTC eCommittee] From: Van Snyder Reply-To: Van.Snyder@jpl.nasa.gov To: sc22wg5 Content-Type: text/plain; charset="ISO-8859-1" Organization: Yes Date: Mon, 09 Oct 2017 11:51:33 -0700 Message-ID: <1507575093.32527.647.camel@math.jpl.nasa.gov> Mime-Version: 1.0 X-Mailer: Evolution 2.32.3 (2.32.3-37.el6) Content-Transfer-Encoding: 7bit X-Source-Sender: Van.Snyder@jpl.nasa.gov X-AUTH: Authorized Sender: owner-sc22wg5@open-std.org Precedence: bulk On Sun, 2017-10-08 at 17:05 +0200, Steve Lionel wrote: This is the current summary of the Fortran 2020 Feature Survey that WG5 has been running since July. It will be updated again in January to reflect any new responses. The purpose of the survey is to collect comments and suggestions from the Fortran user community on features they would like to see in the next Fortran standard. No obligation to implement any of the suggestions is implied. N Number Title (Description) Exp. Action Due Date Version Date 2142 Fortran 2020 Feature Survey Results 2017-10 INFO None 2017-10-08 A few comments on the comments: There's a lot of hidden duplication. There are many requests for things we've been asked to do many times before, such as short-circuit logical operators, default initial values for absent arguments, automatic initialization without SAVE, first-class enumeration types.... Some interesting things are well hidden. For example, one responder requested iterators under the rubric of generic programming. Iterators are to coroutines as functions are to subroutines. We shouldn't do one without the other. If we had added coroutines when we added unlimited polymorphic, and had allowed to specify a coroutine in an I/O statement to handle list elements, we might not have done UDDTIO. A little bit more forward thinking would be useful. Another interesting one was extensible modules. Submodules are extensible. They were consciously based on Ada private child units. Ada has had public child units (read "extensible modules") since 1995. This was proposed during discussion of submodules, but rejected. Units of measure were requested several times, but weren't on the "what's your rank for this" list. At least one responder suggested publishing trial balloons as TS's. Proposals to publish a non-binding TS on units, i.e., a trial balloon, have been vociferously resisted.