From owner-sc22wg5@dkuug.dk  Wed May 28 01:00:02 2003
Received: (from majordom@localhost)
	by dkuug.dk (8.12.8p1/8.9.2) id h4RN02x4073390
	for sc22wg5-domo; Wed, 28 May 2003 01:00:02 +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 taka.swcp.com (taka.swcp.com [198.59.115.12])
	by dkuug.dk (8.12.8p1/8.9.2) with ESMTP id h4RMxqEc073369
	for <sc22wg5@dkuug.dk>; Wed, 28 May 2003 00:59:58 +0200 (CEST)
	(envelope-from walt@fortran.com)
Received: from fortran.com ([65.121.119.54])
	by taka.swcp.com (8.12.9/8.12.9) with ESMTP id h4RN0rKE039324;
	Tue, 27 May 2003 17:00:54 -0600 (MDT)
Message-ID: <3ED3EE0D.5010100@fortran.com>
Date: Tue, 27 May 2003 16:00:29 -0700
From: Walt Brainerd <walt@fortran.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.0.2) Gecko/20021120 Netscape/7.01
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: j.k.reid@rl.ac.uk, sc22wg5@dkuug.dk
Subject: Re: (SC22WG5.2729) Name of the language
References: <200305022236.h42MaukZ085984@dkuug.dk> <200305221604.h4MG48S1032762@dkuug.dk>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Status: No, hits=-1.0 required=10.0
	tests=REFERENCES,USER_AGENT_MOZILLA_UA
	version=2.54
X-Spam-Level: 
X-Spam-Checker-Version: SpamAssassin 2.54 (1.174.2.17-2003-05-11-exp)
Sender: owner-sc22wg5@dkuug.dk
Precedence: bulk

John Reid wrote

> Comments, please.

Since I was the guy that proposed this before, I
guess you all know my opinion, but here is more:

I think the important thing is to "get it right",
rather than worry about what might confuse some
people or worrying about what might happen in 2008.

There may be a few articles and references to f2k
out there, but I think that is among the knowledgable
and they can adjust pretty easily. I think it is
very wg5/j3-centered to think that there are very
many out there who really know much about the next
standard. [I am still making a pretty good living
telling people about Fortran 90.]

And finally, it is always risky to implement anything
(compilers, books, tutorials, etc.) based on what is
in a draft standard :-).

The following algorithm has determined all of the
previous names (some were not official, of course):

program fortran_name
  character(len=8) :: date
  call date_and_time(date=date)
  print *, "Official name: ", "Fortran " // date(3:4)
  print *, "Short name: ", "F" // date(3:4)
end program fortran_name

To respond to one comment, F03 is just as easy as
F2k. I am not sure why we are hung up on having to
include the century this time, but I think that is
better than using a year in the wrong millenium.

I also think Malcolm's suggestion of 2002 is close
enough and has some other nice features.

-- 
Walt Brainerd         +1-877-355-6640 (voice & fax)
The Fortran Company   +1-520-760-1397 (outside USA)
6025 N. Wilmot Road   walt@fortran.com
Tucson, AZ 85750 USA  http://www.fortran.com



