From owner-sc22wg5+sc22wg5-dom9=www.open-std.org@open-std.org  Mon Jun 29 19:12:11 2020
Return-Path: <owner-sc22wg5+sc22wg5-dom9=www.open-std.org@open-std.org>
X-Original-To: sc22wg5-dom9
Delivered-To: sc22wg5-dom9@www.open-std.org
Received: by www.open-std.org (Postfix, from userid 521)
	id 9BB783589E3; Mon, 29 Jun 2020 19:12:11 +0200 (CEST)
Delivered-To: sc22wg5@open-std.org
X-Greylist: delayed 328 seconds by postgrey-1.34 at www5.open-std.org; Mon, 29 Jun 2020 19:12:11 CEST
Received: from wout2-smtp.messagingengine.com (wout2-smtp.messagingengine.com [64.147.123.25])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by www.open-std.org (Postfix) with ESMTP id 26BC33568AC
	for <sc22wg5@open-std.org>; Mon, 29 Jun 2020 19:12:10 +0200 (CEST)
Received: from compute1.internal (compute1.nyi.internal [10.202.2.41])
	by mailout.west.internal (Postfix) with ESMTP id 2029BA04
	for <sc22wg5@open-std.org>; Mon, 29 Jun 2020 13:06:38 -0400 (EDT)
Received: from imap21 ([10.202.2.71])
  by compute1.internal (MEProxy); Mon, 29 Jun 2020 13:06:38 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=certik.us; h=
	mime-version:message-id:date:from:to:subject:content-type; s=
	fm3; bh=Ama13/ZLW03yfQorjD+m8sFJW8mF8w6O08KNG3j1skI=; b=ZVbUhFWl
	sCjB72dFHAXcatia5SCgco4D7WehFxjO9MxSHlFRNqXpB7jXe4kjpH7VhHaw1LhF
	LscI1gtMhcveGIYrwI91Q1KDgPa7wWELX5AHyc76PQyRpqBf+wpIhGZii3E0lTda
	YhPqBryvNLdPQVfMYjNaANmXVTpAZq7UBbh6RAAzh10oUEUa/TfVK6G5VQTVCfss
	qmG+c+IfbzA2F6DqPm09EAB4+EHd+7rUUDjnjIBb407sKz1h2Yeo3jaJq4oSoq+i
	eLNQnHCvYQ9Vu8e2EOMX9LZpDYWEjvriyhyv5LP4xnEdxbNYZMlIq8twc2W2UWxa
	BWyo6wNqlMaKyA==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=
	messagingengine.com; h=content-type:date:from:message-id
	:mime-version:subject:to:x-me-proxy:x-me-proxy:x-me-sender
	:x-me-sender:x-sasl-enc; s=fm3; bh=Ama13/ZLW03yfQorjD+m8sFJW8mF8
	w6O08KNG3j1skI=; b=hFWjfuT7XWGwuSjTLQC0cc1hsIvDr8LQ44dJe4Hk3iztS
	PL5SFeC5m6qKTm+bpbb2t6LNUHCx+vmrBaOuCgnUS6FtpuJOiksTGrZ/W/e1tpF+
	gSht4dzKc7W1WB04ipjtpFLQGVkh71TGdv6g5R7tjpHEyifSdQHrFbbm2WJvuXaG
	/hfd73tgptvXcDR+DhI0r2uMaYOa2W0UdkOpf+fwNgII5tc6NlsLBygRWhWfKXOa
	tH8FVqnzKP+OaFqCkDxdwG3EwPNG6ZVViQVxrAgCkhc1HwH+8vKKUi/hu7bGfZcv
	0tp5eNSATaGaDyOe3NxUJtKT8m9mt5ptuK/Z9CFvQ==
X-ME-Sender: <xms:nR_6XsZi1pjnb7ECLgpFDibwZ-xncbq4rCAjN-b3KFnEY8N_93mCqQ>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduhedrudelledgfeeiucetufdoteggodetrfdotf
    fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen
    uceurghilhhouhhtmecufedttdenucenucfjughrpefofgggkfffhffvufgtsehttdertd
    erreejnecuhfhrohhmpefqnhgurhgvjhgpvegvrhhtvohkuceoohhnughrvghjsegtvghr
    thhikhdruhhsqeenucggtffrrghtthgvrhhnpefhgfektedtkeeiieekgfevhfdtfeethe
    eiudeiffdthffhieeghfehgedtieffhfenucevlhhushhtvghrufhiiigvpedtnecurfgr
    rhgrmhepmhgrihhlfhhrohhmpehonhgurhgvjhestggvrhhtihhkrdhush
X-ME-Proxy: <xmx:nR_6XnYOhLpL9fEwOHCFt96xDW4gcztpJkMTyCgW_8FwcwzE5Ksmpg>
    <xmx:nR_6Xm-EYK-B-17pg324vWDqayvNxumyL1_-G8H4Sz9-LW9MRifD-w>
    <xmx:nR_6XmqJSwBM8L2NRnJVC9pG53pNPoTaKc3FDCc58qiP6escNY6Axw>
    <xmx:nR_6Xs4gZ_zbPuruDiNKJEJiHZDADRUU3KF6_6HnwFumnvD1n12yEQ>
Received: by mailuser.nyi.internal (Postfix, from userid 501)
	id 28EBE660081; Mon, 29 Jun 2020 13:06:37 -0400 (EDT)
X-Mailer: MessagingEngine.com Webmail Interface
User-Agent: Cyrus-JMAP/3.3.0-dev0-576-gfe2cd66-fm-20200629.001-gfe2cd668
Mime-Version: 1.0
Message-Id: <b6287cfd-7c9f-4299-b335-1de05c1a65cf@www.fastmail.com>
Date: Mon, 29 Jun 2020 11:06:03 -0600
From: =?UTF-8?Q?Ond=C5=99ej_=C4=8Cert=C3=ADk?= <ondrej@certik.us>
To: "WG5 List" <sc22wg5@open-std.org>
Subject: Interp ballot #36 response for "LANL"
Content-Type: text/plain
Sender: owner-sc22wg5@open-std.org
Precedence: bulk

The following Fortran interpretations are being balloted:

Yes  No   Number    Title

-Y-  ---  F18/015  Example in C.6.8 is wrong
-Y-  ---  F18/016  Host association changes in Fortran 2018
---  -N-  F18/017  Final subroutine invocation order
-Y-  ---  F18/018  Public namelist and private variable

The explanation for NO on F18/017:

As we see it, the core conflict is between the finalization order prescribed by 7.5.6.2 and what is considered finalizable. The interp as it stands resolves this conflict (and the double finalization) by sacrificing the former to preserve the latter. This interp argues that including allocatables in the ordering in 7.5.6.2 was a design error, or never intended to be understood as such. We think the opposite; ignoring allocatable components in the definition of a finalizable type was the error, and that 7.5.6.2 as it stands does imply the finalization of allocatables and should continue to do so since it is the more useful behavior for users. Thus we suggested edits to do the opposite of the interp: preserve the finalization order by sacrificing the existing definition of finalizable. The effect is not to change the design of the standard, but rather to preserve what we see as the intended design expressed in 7.5.6.2.
