From owner-sc22wg5+sc22wg5-dom8=www.open-std.org@open-std.org  Tue Feb 11 08:40:50 2014
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 C82189DB18A; Tue, 11 Feb 2014 08:40:50 +0100 (CET)
Delivered-To: sc22wg5@open-std.org
Received: from mail.jpl.nasa.gov (smtp.jpl.nasa.gov [128.149.139.105])
	by www.open-std.org (Postfix) with ESMTP id 3C3EF9DB189
	for <sc22wg5@open-std.org>; Tue, 11 Feb 2014 08:40:49 +0100 (CET)
Received: from [10.128.119.43] (66.237.29.114.ptr.us.xo.net [66.237.29.114])
	(authenticated (0 bits))
	by smtp.jpl.nasa.gov (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.1) with ESMTP id s1B7eRSm028129
	(using TLSv1/SSLv3 with cipher DHE-RSA-AES256-SHA (256 bits) verified NO)
	for <sc22wg5@open-std.org>; Mon, 10 Feb 2014 23:40:29 -0800
Subject: Concerned about the coarray TS
From: Van Snyder <van.snyder@jpl.nasa.gov>
To: sc22wg5 <sc22wg5@open-std.org>
Content-Type: text/plain; charset="ISO-8859-1"
Date: Mon, 10 Feb 2014 23:40:44 -0800
Message-ID: <1392104444.3037.28.camel@van-laptop>
Mime-Version: 1.0
X-Mailer: Evolution 2.32.3 (2.32.3-30.el6) 
Content-Transfer-Encoding: 7bit
X-Source-Sender: van.snyder@jpl.nasa.gov
X-JPL-Spam-Score': 80%
Sender: owner-sc22wg5@open-std.org
Precedence: bulk

I'm concerned that the coarray TS is becoming unnecessarily complicated.
I think there are much easier ways to accomplish what it appears to be
trying to accomplish.  I've put 14-118 on the J3 server as an outline of
what I think is a much simpler scheme.  It amplifies ideas I proposed
informally at Delft.

Van


