Path: utzoo!attcan!uunet!lll-winken!ames!mailrus!csd4.milw.wisc.edu!uxc!uxc.cso.uiuc.edu!uxg.cso.uiuc.edu!uxe.cso.uiuc.edu!hirchert
From: hirchert@uxe.cso.uiuc.edu
Newsgroups: comp.lang.fortran
Subject: Re: An exercise in futility (was Result
Message-ID: <50500098@uxe.cso.uiuc.edu>
Date: 13 Jan 89 17:49:00 GMT
References: <583@mbph.UUCP>
Lines: 25
Nf-ID: #R:mbph.UUCP:583:uxe.cso.uiuc.edu:50500098:000:1125
Nf-From: uxe.cso.uiuc.edu!hirchert    Jan 13 11:49:00 1989


Daniel R. Levy(levy@ttrdc.UUCP) asks:
>In article <207@mic.UUCP>, d25001@mic.UUCP (Carrington Dixon) writes:
>> The X3.9-1978 not only madates that identifiers be
>> no more than six characters long; it also defines the character set as
>> consisting _ONLY_ of the UPPER-CASE letters.

>Could someone please quote chapter and verse.

Page 3-2, lines 1-3 (section 3.1.5, paragraph 2):

"Except for the currency symbol, the graphics used for the
 forty-nine characters must be as given in 3.1.1, 3.1.2, and
 3.1.4.  However, the style of any graphic is not specified."

The graphics given 3.1.1 are upper-case letters.

Note that this does _not_ prevent a vendor from mapping linker externals to
lower case.  (The operation of the linker is invisible insofar as the FORTRAN
standard is concerned.)  Likewise, it does not prevent a FORTRAN OPEN statement
from accepting lower-case keyword values (as an extension) as long as the
upper-case versions are accepted, too.  It _does_ mandate that the values
returned by INQUIRE (other than file name) must be in upper-case.

Stu Feldman's a bright guy, but this is one he got wrong.