Path: utzoo!utgpu!attcan!uunet!lll-winken!csd4.milw.wisc.edu!bionet!ames!amdahl!pyramid!nsc!versatc!mips!prls!philabs!ttidca!hollombe
From: hollombe@ttidca.TTI.COM (The Polymath)
Newsgroups: comp.sys.ibm.pc
Subject: Re: FORTRANish C (was Re: Hungarian C C
Message-ID: <4295@ttidca.TTI.COM>
Date: 21 Apr 89 00:13:38 GMT
References: <2701@garth.UUCP> <45900223@uxe.cso.uiuc.edu>
Reply-To: hollombe@ttidcb.tti.com (The Polymath)
Organization: The Cat Factory
Lines: 23

In article <45900223@uxe.cso.uiuc.edu> mcdonald@uxe.cso.uiuc.edu writes:
}Except that in Fortran the naming AUTOMATICALLY makes the variable
}the correct type! If you see a variable in a normal (i.e. it uses
}this method, which is not required) Fortran program, you can tell the
}type directly from the name.

The last FORTRAN shop I worked in considered this a hazardous practice.
So much so, in fact, that their in-house coding standard required an

	IMPLICIT COMPLEX (A-Z)

at the top of every module to force explicit declaration of every
variable.  If we found something defined as complex in the link map, we
knew our wrist had been slapped.  (We also had a dandy data-dictionary
system that automatically put headers on each module containing all
information about each variable used.  It even included the appropriate
common blocks for us.  Saved a lot of grief).

-- 
The Polymath (aka: Jerry Hollombe, hollombe@ttidca.tti.com)  Illegitimati Nil
Citicorp(+)TTI                                                 Carborundum
3100 Ocean Park Blvd.   (213) 452-9191, x2483
Santa Monica, CA  90405 {csun|philabs|psivax}!ttidca!hollombe