From owner-sc22wg5+sc22wg5-dom8=www.open-std.org@open-std.org  Wed Mar 14 13:13:19 2012
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 E7CA93569A7; Wed, 14 Mar 2012 13:13:19 +0100 (CET)
Delivered-To: sc22wg5@open-std.org
Received: from ppsw-50.csi.cam.ac.uk (ppsw-50.csi.cam.ac.uk [131.111.8.150])
	by www.open-std.org (Postfix) with ESMTP id 6549F35684F
	for <sc22wg5@open-std.org>; Wed, 14 Mar 2012 13:13:18 +0100 (CET)
X-Cam-AntiVirus: no malware found
X-Cam-SpamDetails: not scanned
X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/
Received: from hermes-2.csi.cam.ac.uk ([131.111.8.54]:50756)
	by ppsw-50.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.157]:25)
	with esmtpa (EXTERNAL:nmm1) id 1S7n4w-0001S4-qD (Exim 4.72) for sc22wg5@open-std.org
	(return-path <nmm1@hermes.cam.ac.uk>); Wed, 14 Mar 2012 12:13:18 +0000
Received: from prayer by hermes-2.csi.cam.ac.uk (hermes.cam.ac.uk)
	with local (PRAYER:nmm1) id 1S7n4w-0000Xk-4o (Exim 4.67) for sc22wg5@open-std.org
	(return-path <nmm1@hermes.cam.ac.uk>); Wed, 14 Mar 2012 12:13:18 +0000
Received: from [83.67.89.123] by webmail.hermes.cam.ac.uk
	with HTTP (Prayer-1.3.4); 14 Mar 2012 12:13:18 +0000
Date: 14 Mar 2012 12:13:18 +0000
From: "N.M. Maclaren" <nmm1@cam.ac.uk>
To: sc22wg5@open-std.org
Subject: Re: [ukfortran] (SC22WG5.4640) Part 2 of the standard
Message-ID: <Prayer.1.3.4.1203141213180.29444@hermes-2.csi.cam.ac.uk>
In-Reply-To: <20120314115650.BE9429DB112@www.open-std.org>
References: <20120313200407.EBAB39DB112@www.open-std.org>
 <20120314115650.BE9429DB112@www.open-std.org>
X-Mailer: Prayer v1.3.4
Mime-Version: 1.0
Content-Type: text/plain; format=flowed; charset=ISO-8859-1
Sender: owner-sc22wg5@open-std.org
Precedence: bulk

On Mar 14 2012, David Muxworthy wrote:
>On 13 Mar 2012 John Reid wrote:
>
>> I promised at Garching to look into the conversion to Fortran 2003 of 
>> the procedures of the varying length strings module that are not 
>> included in Part 1 of the Standard. These are the I/O procedures GET, 
>> PUT and PUT_LINE and the substring manipulation procedures EXTRACT, 
>> INSERT, REMOVE, REPLACE, and INSERT.
>
> This was undertaken in the context that provision of an updated module 
> would allow withdrawal of the standard. Since then we have had the 
> results of the systematic review of the standard (11 confirm, 2 
> stabilize, 19 abstain) so formally the standard is confirmed until the 
> next review in 2016.
>
> The review also showed that a surprising number of countries (7) have 
> national standards identical to the ISO one and five answered 'yes' to: 
> "Is this International Standard used in your country without national 
> adoption or are products used in your country based on this standard?".
>
>It would seem best for WG5 to do nothing more for the time being.

I disagree that WG5 should do absolutely nothing.

The second half of the context was to consider, in the light of John's
experience, whether it was desirable to add any new intrinsics, on the
grounds that implementing them using existing facilities is  unnecessarily
error-prone or inefficient.  I feel that WG5 should still consider that
question.


Regards,
Nick Maclaren.

