From owner-sc22wg5@dkuug.dk  Tue Jun 17 08:25:53 2003
Received: (from majordom@localhost)
	by dkuug.dk (8.12.8p1/8.9.2) id h5H6PrLg005801
	for sc22wg5-domo; Tue, 17 Jun 2003 08:25:53 +0200 (CEST)
	(envelope-from owner-sc22wg5@dkuug.dk)
X-Authentication-Warning: ptah.dkuug.dk: majordom set sender to owner-sc22wg5@dkuug.dk using -f
Received: from brmea-mail-2.sun.com (brmea-mail-2.Sun.COM [192.18.98.43])
	by dkuug.dk (8.12.8p1/8.9.2) with ESMTP id h5H6PiEc005796
	for <sc22wg5@dkuug.dk>; Tue, 17 Jun 2003 08:25:48 +0200 (CEST)
	(envelope-from corbett@mpkmail.eng.sun.com)
Received: from engmail2sun.Eng.Sun.COM ([129.144.134.19])
	by brmea-mail-2.sun.com (8.12.9/8.12.9) with ESMTP id h5H6PhYU015288;
	Tue, 17 Jun 2003 00:25:43 -0600 (MDT)
Received: from phys-mpkmaila (phys-mpkmaila.SFBay.Sun.COM [129.146.18.131])
	by engmail2sun.Eng.Sun.COM (8.12.9+Sun/8.12.9/ENSMAIL,v2.2) with ESMTP id h5H6PgGq003026;
	Mon, 16 Jun 2003 23:25:42 -0700 (PDT)
Received: from lupa (lupa.Eng.Sun.COM [129.146.78.104])
 by mpkmail.eng.sun.com (iPlanet Messaging Server 5.2 Patch 1 (built Apr  2
 2002)) with SMTP id <0HGM00C7I4IUAX@mpkmail.eng.sun.com>; Mon,
 16 Jun 2003 23:25:42 -0700 (PDT)
Date: Mon, 16 Jun 2003 23:25:42 -0700 (PDT)
From: Robert Corbett <corbett@mpkmail.eng.sun.com>
Subject: Re: (SC22WG5.2760) Type-spec
To: Richard.Maine@nasa.gov
Cc: sc22wg5@dkuug.dk
Reply-to: Robert Corbett <corbett@mpkmail.eng.sun.com>
Message-id: <0HGM00C7J4IUAX@mpkmail.eng.sun.com>
MIME-version: 1.0
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.4.8 SunOS 5.8 sun4u sparc
Content-type: TEXT/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Content-MD5: 79lw84tbrvVu6x0jYAsHbQ==
Sender: owner-sc22wg5@dkuug.dk
Precedence: bulk

> (I also could swear that you were the person who asked the question
> that prompted this sentence to be added, and even had an
> implementation that didn't act this way...but I could be mistaken.)

I have tried, on several occasions, to convince J3 to use the
terminology regarding data types originally specifed in
Sections 2.4.1 and 4 of the Fortran 90 standard throughout
the standard.  To date, J3 has gone in the other direction.
The change of the title of Chapter 4  from *Intrinsic and
derived data type" to "Types" demonstrates to me that J3 no
longer understands that the Fortran 90 standard gives the
phrase "data type" special meaning beyond that of the word
"type."

I shall give again the most obvious example where there is
a contradiction between the body of the standard and the
terminology regarding data types.  Section 2.4.1.1 states

    The intrinsic types are integer, real, complex,
    character, and logical.

Section 4 reiterates that statement.  Note that there is no
intrinsic type "double precision real."  Yet Section 5.1.1.3
of the Fortran 90 standard states

    The DOUBLE PRECISION type specifier specifies that
    all entities whose names are declared in this
    statement are of intrinsic type double precision
    real (4.3.1.2).

Section 5.1.1.3 of J3/03-007 states

    The DOUBLE PRECISION type specifier is used to declare
    entities of intrinsic type double precision real (4.4.2).
    
Section 5.1.1.3 should long ago have been replaced with a
statement equivalent to

    The DOUBLE PRECISION type specifier is used to declare
    entities of intrinsic type real.  The kind type parameter
    value is KIND(0.0D0).  The entities declared are of type
    double precision real.

					Sincerely,
					Bob Corbett

