From jwagener@ionet.net Thu Nov 23 21:02:41 1995 Received: from ion3.ionet.net (ion3.ionet.net [204.96.200.8]) by dkuug.dk (8.6.12/8.6.12) with ESMTP id VAA06414 for ; Thu, 23 Nov 1995 21:02:38 +0100 Received: from erehwon (tsip24.ionet.net [206.28.164.33]) by ion3.ionet.net (8.6.12/8.6.12) with SMTP id OAA07582 for ; Thu, 23 Nov 1995 14:02:23 -0600 X-Mailer: InterCon TCP/Connect II 2.2.1 MIME-Version: 1.0 Message-Id: <9511231407.AA56380@erehwon> Date: Thu, 23 Nov 1995 14:07:56 -0500 From: "Jerrold L. Wagener" To: sc22wg5@dkuug.dk Subject: Liaison Report on Allocatable Components TR Content-Transfer-Encoding: Quoted-Printable Content-Type: Text/Plain; charset=ISO-8859-1 Content-Disposition: Inline X3J3/95-308r1 Liaison Report on Allocatable Components TR To: X3J3, WG5, Malcolm Cohen From: X3J3/parallel References: X3J3/95-272 Date: Nov 16, 1995 This report is based on the Nov 8 version of the Data Type Enhancements = in Fortran paper, X3J3/95-272. The paper describes enhancements = to allocatable objects and parameterized data types. This report = primarily refers to the requirements section (3.1) for allocatable = objects. The detailed edits to the standard, section 4.1, have not = been examined in detail. This facility regularizes the allocatable attribute by providing: =B0 Allocatable array components in derived types, =B0 Allocatable array dummy arguments, =B0 Allocatable array function results, =B0 A set of rules and constraints generally like those for existing allocatable arrays and/or pointer objects for the new=20 allocatable objects. X3J3 concurs with this facility. X3J3 has technical concerns in the following areas: =B0 The description of when allocatable function results are or may be deallocated needs to be clarified, perhaps with an example like SUM(f(1)) + f(1) + f(2). =B0 Explicit deallocation of a function result within the function needs to be discussed. =B0 Can or must allocatable functions be PURE or ELEMENTAL? =B0 Can allocatable functions be used in a WHERE or FORALL construct? =B0 Do allocatable functions interact with copy-in/out and Interpretation 125? =B0 Does the description of allocatable components need to be modified now that components can be DIRECT and/or ULTIMATE? =B0 The derived type constructor is somewhat awkward with allocatable components and there is a hint that another method is possible; could this be discussed? Some of these concerns may reflect minor or nonexistent problems; = others may be major problems. These concerns have been raised = by individuals and subgroups with X3J3 and have not been analyzed in = detail by X3J3; the result of any such analysis may conclude there is = no problem associated with a specific item or that there are other = problems not identified. Despite this lack of detailed analysis, = X3J3 believes that this list of concerns should be addressed by = the development body for data type enhancements.