From owner-sc22wg5@open-std.org  Fri Feb  5 12:58:44 2010
Return-Path: <owner-sc22wg5@open-std.org>
X-Original-To: sc22wg5-dom8
Delivered-To: sc22wg5-dom8@www2.open-std.org
Received: by www2.open-std.org (Postfix, from userid 521)
	id 14772C3BA07; Fri,  5 Feb 2010 12:58:44 +0100 (CET)
X-Original-To: sc22wg5@open-std.org
Delivered-To: sc22wg5@open-std.org
X-Greylist: delayed 571 seconds by postgrey-1.18 at www2.open-std.org; Fri, 05 Feb 2010 12:58:42 CET
Received: from mk-filter-4-a-1.mail.uk.tiscali.com (mk-filter-4-a-1.mail.uk.tiscali.com [212.74.100.55])
	by www2.open-std.org (Postfix) with ESMTP id ECE25C3BA06
	for <sc22wg5@open-std.org>; Fri,  5 Feb 2010 12:58:42 +0100 (CET)
X-Trace: 335989132/mk-filter-4.mail.uk.tiscali.com/B2C/$b2c-THROTTLED-DYNAMIC/b2c-CUSTOMER-DYNAMIC-IP/88.106.75.240/None/d.muxworthy@bcs.org.uk
X-SBRS: None
X-RemoteIP: 88.106.75.240
X-IP-MAIL-FROM: d.muxworthy@bcs.org.uk
X-SMTP-AUTH: 
X-Originating-Country: GB/UNITED KINGDOM
X-MUA: Apple Mail (2.753.1)
X-IP-BHB: Once
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgQBALaUa0tYakvw/2dsb2JhbAAI1xqCSYIDBA
X-IronPort-AV: E=Sophos;i="4.49,412,1262563200"; 
   d="scan'208";a="335989132"
Received: from 88-106-75-240.dynamic.dsl.as9105.com (HELO [192.168.1.2]) ([88.106.75.240])
  by smtp.tiscali.co.uk with ESMTP; 05 Feb 2010 11:49:09 +0000
Mime-Version: 1.0 (Apple Message framework v753.1)
Content-Transfer-Encoding: quoted-printable
Message-Id: <B2653290-C9A5-484E-B97F-6952A5174E45@bcs.org.uk>
Content-Type: text/plain; charset=WINDOWS-1252; delsp=yes; format=flowed
To: sc22wg5@open-std.org
From: David Muxworthy <d.muxworthy@bcs.org.uk>
Subject: Re: (SC22WG5.4147) Urgent: letter ballot on interps
Date: Fri, 5 Feb 2010 11:50:35 +0000
X-Mailer: Apple Mail (2.753.1)
Sender: owner-sc22wg5@open-std.org
Precedence: bulk

Yes  No Number     Title
-Y- --- F95/0098 Are dummy functions returning assumed-length =20
character legal?
-Y- --- F03/0022 Coexistence of IEEE and non-IEEE kinds
-Y- --- F03/0024 DEALLOCATE and array pointers
-C- --- F03/0034 IEEE_LOGB()
-Y- --- F03/0039 HYPOT()
-C- --- F03/0063 Procedure pointers in BLOCK DATA program units
-Y- --- F03/0071 Subroutine/function ambiguity in generics
-Y- --- F03/0078 IEEE_SUPPORT_DATATYPE vs. mathematical equivalence
-Y- --- F03/0090 Polymorphic array constructors
-Y- --- F03/0112 Attributes allowed for dummy arguments in defined =20
assignments
-Y- --- F03/0119 Elemental procedures and deferred length character =20
components
-Y- --- F03/0122 When do objects of sequence derived type have the =20
same type?
-Y- --- F03/0125 Definitions of EXTENDS_TYPE_OF and SAME_TYPE_AS
-Y- --- F03/0126 References to VOLATILE variables in pure procedures
-Y- --- F03/0127 Duration of procedure execution
-Y- --- F03/0129 C_LOC of character substrings
-Y- --- F03/0130 Elemental specific intrinsic procedure characteristics
-Y- --- F03/0131 SAVE attribute and EQUIVALENCE
-Y- --- F03/0132 Unformatted i/o and private components
-Y- --- F03/0133 Is unlimited polymorphic allowed in COMMON?
-Y- --- F03/0134 Implicit typing of procedure pointers
-C- --- F03/0135 Interaction between RESULT, recursion, and host generic
-Y- --- F03/0136 Are subroutines distinguishable from arrays?
-Y- --- F03/0137 Dummy procedure type compatibility
-C- --- F03/0138 External <procedure-name> as <proc-target>
-Y- --- F03/0139 Functions returning procedure pointers
-Y- --- F03/0140 Type of nested construct entities
-Y- --- F03/0141 More than one specific interface for a procedure



F03/0034 IEEE_LOGB()
The style of the two new cases would be more consistent with that of
the existing cases if the order of the conditions were reversed ("If X
is infinite and IEEE_SUPPORT_INF(X) is true ..." etc).  This applies
also to F2008.

F03/0063 Procedure pointers in BLOCK DATA program units
Nit-pick: In the edit for [98:21] "allocatable" should read
"allocatable,"

F03/0135 Interaction between RESULT, recursion, and host generic
The edit at [276:36+] should read "that scoping unit" rather than "the
scoping unit" for consistency with the other cases.

F03/0138 External <procedure-name> as <proc-target>
The proposed edit results in rather opaque English.  Changing
"association, referenced" to "association and is referenced" gives a
slight improvement.  The constraint would then be:

   A <procedure-name> shall be the name of a module or dummy procedure,
   a specific intrinsic function listed in 13.6 and not marked with a
   bullet (=95), a procedure pointer, or an external procedure that is
   accessed by USE or host association and is referenced in the scoping
   unit as a procedure, or that has the EXTERNAL attribute.


David Muxworthy

