From owner-sc22wg5+sc22wg5-dom8=www.open-std.org@open-std.org  Sun Jul 10 23:28:10 2016
Return-Path: <owner-sc22wg5+sc22wg5-dom8=www.open-std.org@open-std.org>
X-Original-To: sc22wg5-dom8
Delivered-To: sc22wg5-dom8@www.open-std.org
Received: by www.open-std.org (Postfix, from userid 521)
	id D641D3584A2; Sun, 10 Jul 2016 23:28:10 +0200 (CEST)
Delivered-To: sc22wg5@open-std.org
Received: from mail.jpl.nasa.gov (sentrion2.jpl.nasa.gov [128.149.139.106])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by www.open-std.org (Postfix) with ESMTP id 53F2D356D0D
	for <sc22wg5@open-std.org>; Sun, 10 Jul 2016 23:28:08 +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 u6ALS3H8014368
	(using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128 bits) verified NO);
	Sun, 10 Jul 2016 14:28:05 -0700
Subject: Re: (j3.2006) (SC22WG5.5770) RE: RE: Other languages with unit
 support
From: Van Snyder <Van.Snyder@jpl.nasa.gov>
Reply-To: Van.Snyder@jpl.nasa.gov
To: fortran standards email list for J3 <j3@mailman.j3-fortran.org>
Cc: WG5 <sc22wg5@open-std.org>
In-Reply-To: <20160710205126.4B64F356F40@www.open-std.org>
References: <20160709230643.A9C96358929@www.open-std.org>
	 <20160710043839.A15433587CC@www.open-std.org>
	 <1468127059.3820.206.camel@vanlap.vsnyder>
	 <F6DD4291-8347-4CD3-AE4A-F300DD898420@cray.com>
	 <1468179688.3820.212.camel@vanlap.vsnyder>
	 <20160710205126.4B64F356F40@www.open-std.org>
Content-Type: text/plain; charset="ISO-8859-1"
Organization: Yes
Date: Sun, 10 Jul 2016 14:28:03 -0700
Message-ID: <1468186083.25709.339.camel@math.jpl.nasa.gov>
Mime-Version: 1.0
X-Mailer: Evolution 2.32.3 (2.32.3-36.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, 2016-07-10 at 20:51 +0000, Whitlock, Stan wrote:
> The draft TS proposal now in N2113 includes the words from C++ TSs
> that say "this was never part of a standard and might not ever be part
> of a standard."  Let's publish it, so that preprocessors can at least
> say "My product conforms to the TS."
> 
> Stan> Are you kidding?  N2113 has not been vetted, edits haven't been
> checked, it is in no way ready for publication as a TS supported by
> WG5 even if it never goes into the standard.  And the committee keeps
> telling you that it doesn't want to do this work.  If you want to
> publish its contents as a paper in, say, The Fortran Forum, then all
> these preprocessors will have something to which they can conform.
> End Stan> 

So how about publishing it without edits?  A quasi-standard for a
preprocessor wouldn't need edits to the standard.  Or with a caveat that
says "These edits have not been checked rigorously, and they apply to
Fortran 2008, not Fortran 2015?"

N2113 is the nineteenth edition of this proposal, in its present form.
This doesn't count my informal proposal to X3J3 in 1986, or the formal
one that was not spelt out in as much detail in 2004.  Eighteen previous
ones have either been WG5 or J3 papers, or some member(s) of one of the
committees commented informally on an earlier draft that wasn't a formal
paper.  Isn't that what "A TS has an independent schedule" means?

Nobody has commented on its technical content since Malcolm suggested to
replace rational-arithmetic exponents in composite unit definitions with
a RATIONAL_POWER intrinsic function.  I perhaps naively assumed that
meant nobody had a comment on the technical content.


