Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!csd4.milw.wisc.edu!zdenko
From: zdenko@csd4.milw.wisc.edu (Zdenko Tomasic)
Newsgroups: comp.lang.fortran
Subject: Re: "arithmetic if":: Re: Feature for the next C version
Message-ID: <3611@csd4.milw.wisc.edu>
Date: 30 Jul 89 01:09:35 GMT
References: <55480@tut.cis.ohio-state.edu> <1989Jul20.152935.14872@utzoo.uucp> <67@motto.UUCP> <18764@mimsy.UUCP> <1389@crdgw1.crd.ge.com> <8515@batcomputer.tn.cornell.edu> <3600@csd4.milw.wisc.edu> <1614@garcon.cso.uiuc.edu>
Sender: news@csd4.milw.wisc.edu
Reply-To: zdenko@csd4.milw.wisc.edu (Zdenko Tomasic)
Organization: University of Wisconsin-Milwaukee
Lines: 24

In article <1614@garcon.cso.uiuc.edu> mcdaniel@uicsrd.csrd.uiuc.edu (Tim McDaniel) writes:
>...
>In FORTRAN 77, you can use the BLANK= attribute on the OPEN statement
>to control whether trailing blanks are ignored or treated as zeroes,
>by
>        BLANK='NULL'
>or      BLANK='ZERO'
>The default is NULL -- by default trailing blanks are simply ignored.
>I don't believe FORTRAN 66 took a stand on the issue, and in its
>default, implementors treated trailing blanks as zeroes.
>
>Briefly, trailing blanks *may be* treated as zeroes.
>

FORTRAN66 required that all trailing blanks be treated as zeros
(see 7.2.3.6 of FORTRAN66, page 20). It is interesting that
FORTRAN77 chose to make a different default. I wonder how many
people have bad experiences porting dusty input decks because of that.
Better yet how many people are aware of either default?
--
___________________________________________________________________
Zdenko Tomasic, UWM, Chem. Dept., P.O. Box 413, Milwaukee, WI 53201
UUCP: uwvax!uwmcsd1!uwmcsd4!zdenko
ARPA: zdenko@csd4.milw.wisc.edu