Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!know!zaphod.mps.ohio-state.edu!wuarchive!julius.cs.uiuc.edu!psuvax1!psuvm!ysub!fc138001
From: FC138001@ysub.ysu.edu (Phil Munro)
Newsgroups: comp.lang.fortran
Subject: Re: Fortran 77 Style Guide (long, REPOST)
Message-ID: <90254.120334FC138001@ysub.ysu.edu>
Date: 11 Sep 90 16:03:34 GMT
References: <26B89BE1.4349@ics.uci.edu> <59012@lanl.gov>
 <1794@ccadfa.adfa.oz.au> <1990Sep10.141639.970@maverick.ksu.ksu.edu>
Distribution: na
Organization: Youngstown State University VM system (YSUB)
Lines: 18

(Myron A. Calhoun) says:
>
>
>Unfortunately, re-used FORMATs cause programs to "break" during maintenance.
>...
>It is EXTREMELY EASY to "guarantee that every FORMAT statement will
>appear immediately under (or in) the [I/O] statement that uses it".
>Just duplicate it.  Shouldn't take more than a few keystrokes per
>FORMAT statement on any reasonable editor; maybe a bit more work if
>one is still using cards!
>
  I think duplicated FORMAT statements mean added memory allocations
when the program is compiled.  Is this not right?

  It seems just as easy to use "any reasonable editor" to find every
use of a FORMAT as to duplicate them and waste memory.  On the other
hand, except for the machine-code memory problem, it is an appealing
idea to put WRITEs and FORMATs together.  --Phil