From owner-sc22wg5+sc22wg5-dom8=www.open-std.org@open-std.org Wed Jul 31 08:26:25 2013 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 A648A9DB146; Wed, 31 Jul 2013 08:26:25 +0200 (CEST) Delivered-To: sc22wg5@open-std.org X-Greylist: delayed 830 seconds by postgrey-1.34 at www5.open-std.org; Wed, 31 Jul 2013 08:26:20 CEST Received: from nag-j.co.jp (nag-j.co.jp [111.68.142.10]) by www.open-std.org (Postfix) with ESMTP id CADBF356920 for ; Wed, 31 Jul 2013 08:26:04 +0200 (CEST) Received: from Maru6 (218-42-159-105.cust.bit-drive.ne.jp [218.42.159.105]) (authenticated bits=0) by nag-j.co.jp (8.14.5/8.14.5) with ESMTP id r6V6PpJH003480; Wed, 31 Jul 2013 06:25:54 GMT (envelope-from malcolm@nag-j.co.jp) Message-ID: <5B885502F95840299A5622B08B876EC2@Maru6> From: "Malcolm Cohen" To: "Erik Kruyt" , "'WG5'" References: <20130724235846.299F4357176@www.open-std.org> <51F0DD9B.6040802@net-b.de><20130725222446.98834357194@www.open-std.org><20130729085936.D199A35717D@www.open-std.org> <20130730212910.B39EB35714F@www.open-std.org> In-Reply-To: <20130730212910.B39EB35714F@www.open-std.org> Subject: Re: [ukfortran] (SC22WG5.5047) RE: ts29113 compiler conformance table Date: Wed, 31 Jul 2013 15:25:50 +0900 Organization: =?UTF-8?B?5pel5pysTkFH?= MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_00C0_01CE8E02.3D4D7BD0" X-Priority: 3 X-MSMail-Priority: Normal Importance: Normal X-Mailer: Microsoft Windows Live Mail 15.4.3555.308 X-MimeOLE: Produced By Microsoft MimeOLE V15.4.3555.308 Sender: owner-sc22wg5@open-std.org Precedence: bulk This is a multi-part message in MIME format. ------=_NextPart_000_00C0_01CE8E02.3D4D7BD0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable > 1. Could you consider to add a line: =E2=80=9CVALUE = attribute=E2=80=9D? Or is this already implied in another feature? =E2=80=9CInteroperability of procedures=E2=80=9D >2. The line =E2=80=9CKind type parameters of integer = specifiers=E2=80=9D is listed in the section =E2=80=9CInput/output = enhancement=E2=80=9D. Could you list this feature under =E2=80=9CData = and object orientation=E2=80=9D? This belongs where it is, =E2=80=9Cinteger specifiers=E2=80=9D is = referring to =E2=80=9Ci/o specifiers=E2=80=9D. I know this list is confusing, but you have to read it (the F2003 part) = in conjunction with N1648. Cheers, --=20 ................................Malcolm Cohen, Nihon NAG, Tokyo. ------=_NextPart_000_00C0_01CE8E02.3D4D7BD0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

1. =20 Could=20 you consider to add a line: =E2=80=9CVALUE attribute=E2=80=9D? Or is = this already implied in=20 another feature?

=E2=80=9CInteroperability=20 of procedures=E2=80=9D

>2. =20 The=20 line =E2=80=9CKind type parameters of integer specifiers=E2=80=9D is = listed in the section=20 =E2=80=9CInput/output enhancement=E2=80=9D. Could you list this feature = under =E2=80=9CData and object=20 orientation=E2=80=9D?

This=20 belongs where it is, =E2=80=9Cinteger specifiers=E2=80=9D is referring = to =E2=80=9Ci/o=20 specifiers=E2=80=9D.

I=20 know this list is confusing, but you have to read it (the F2003 part) in = conjunction with N1648.

Cheers,

--=20
................................Malcolm Cohen, Nihon NAG,=20 Tokyo.
------=_NextPart_000_00C0_01CE8E02.3D4D7BD0--