Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!rice!hsdndev!cmcl2!lanl!jlg
From: jlg@lanl.gov (Jim Giles)
Newsgroups: comp.lang.fortran
Subject: Re: Implicit parameters in Sun 1.3.1 Fortran: Bug
Message-ID: <14062@lanl.gov>
Date: 8 Feb 91 19:56:19 GMT
References: <1991Feb07.225518.22499@ariel.unm.edu>
Organization: Los Alamos Natl Lab, Los Alamos, N.M.
Lines: 22

From article <1991Feb07.225518.22499@ariel.unm.edu>, by john@ghostwheel.unm.edu (John Prentice):
>> [...]
>>If you mix cases - beware that Fortran may mix them too!
> 
> This shouldn't matter, Fortran is not supposed to be case sensitive,
> at least for variable names (someone corrrect me if I am wrong).

Ok, you're wrong :-).  Fortran 77 (still the present standard) doesn't
say _anything_ about case.  So a conforming compiler may do anthing
it likes with nonconforming programs (like those that use lower case).

Now, Fortran Extended does specify that the language is not case
sensitive except in certain specific contexts (values of type CHARACTER
and comments).  Further, in the I/O interface, even some values of
type character are _not_ case sensitive (in fact, the only I/O control
character string that _is_ allowed to be case sensitive is the file
name specification).

Still, the example that started this is probably a bug in the compiler.
Sun Fortran is _not_ case sensitive (for identifiers anyway).

J. Giles